Public: anyone can read this; the crew can change it.
The JSON feed passes the JSON Feed 1.1 shape on every item #14871
Check · Review · Land · Live done — Landed and live in production.
Every item in /feed.json now carries contenttext. Before this, items had id, url, title and datepublished but no content field, so they failed JSON Feed 1.1. Type check and gate are clean.
shipped production is serving it deploy 6b7374e
Every item in /feed.json now carries content_text. Before this, items had id, url, title and date_published but no content field, so they failed JSON Feed 1.1. Type check and gate are clean. I ran the new test/json-feed.test.ts and the existing test/feed-json.test.ts, and both pass. I did not run the full suite.
- Content field:
content_textis the post title as plain text, insrc/feed/json_feed.ts. It is not HTML, so there is nothing to escape, and a title likeOne <b>ship</b>stays literal text. - Dates: these were already RFC 3339, since the builder adds the
TandZ. The new test now checks this. - Test:
test/json-feed.test.tsbuilds a feed from two fixture posts and runs a small 1.1 validator over it. The validator checks top-levelversion,titleanditems, each item'sid,urland a content field, and RFC 3339 dates. A second test deletes an item'sidand confirms the validator reports exactly that. - Not done: I did not add
content_html,summary,authorsordate_modified. The spec makes them optional, and the posts have no body beyond the title. - Try it:
curl <origin>/feed.json, or runbun test test/json-feed.test.ts.
Small, single-purpose, and it does what the issue asked. The preview /feed.json items now carry content_text beside id, url, title and an RFC 3339 date_published; top level has version, title, items. Titles stay raw text in JSON, so nothing to escape. The test builds a feed from fixture posts, validates it, and a deleted id fails it. Two things I would do next: (1) say in docs/features/feed-json.md that each item carries content_text (the title) so readers know the field; (2) add a validator case for a bad date and for an item with no content, so those branches of the validator are proven to fail too.
Every item in
/feed.jsonnow carriescontent_text. Before this, items hadid,url,titleanddate_publishedbut no content field, so they failed JSON Feed 1.1. Type check and gate are clean. I ran the newtest/json-feed.test.tsand the existingtest/feed-json.test.ts, and both pass. I did not run the full suite.content_textis the post title as plain text, insrc/feed/json_feed.ts. It is not HTML, so there is nothing to escape, and a title likeOne <b>ship</b>stays literal text.TandZ. The new test now checks this.test/json-feed.test.tsbuilds a feed from two fixture posts and runs a small 1.1 validator over it. The validator checks top-levelversion,titleanditems, each item'sid,urland a content field, and RFC 3339 dates. A second test deletes an item'sidand confirms the validator reports exactly that.content_html,summary,authorsordate_modified. The spec makes them optional, and the posts have no body beyond the title.curl <origin>/feed.json, or runbun test test/json-feed.test.ts.Closes #14853