Supporting custom namespaces?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- backend
Research direction
No source file or test is named in the issue. Start by locating the RSS/Atom parser entry point and its handling of element names, then use the sample feed to check whether the custom books:bookid field is preserved alongside standard fields.
Written by the indexing model from the issue text.
Description
Hey there, love what you're doing here Dave to make things simple and easy to use :)
Question - should this parse custom namespaces? For example, I'm playing around with adding structured data for a "books" rss project and made a mockup here:
https://wooden-honorable-kale.glitch.me/feed.xml
So this code:
<item>
<title>Testing new fields</title>
<description>Some description </description>
<pubDate>Thu, 16 Jun 2022 00:00:00 +0000</pubDate>
<books:bookid>https://openlibrary.org/works/OL19098683W</books:bookid>
<link>http://tomcritchlow.com/2022/06/16/rejecting-specialization/</link>
<guid isPermaLink="true">http://tomcritchlow.com/2022/06/16/rejecting-specialization/</guid>
</item>
Get's parsed using reallysimple as:
{
"title": "Testing new fields",
"description": "Some description",
"pubDate": "2022-06-16T00:00:00.000Z",
"link": "http://tomcritchlow.com/2022/06/16/rejecting-specialization/",
"guid": "http://tomcritchlow.com/2022/06/16/rejecting-specialization/"
}
Ideally I'd like to generate something like this:
{
"title": "Testing new fields",
"description": "Some description",
"pubDate": "2022-06-16T00:00:00.000Z",
"books:bookid":"https://openlibrary.org/works/OL19098683W"
"link": "http://tomcritchlow.com/2022/06/16/rejecting-specialization/",
"guid": "http://tomcritchlow.com/2022/06/16/rejecting-specialization/"
}
I'm a bit of a coding beginner (and not sure if I coded the custom namespace correctly?) so forgive me if this doesn't make sense or I'm doing something wrong
- Dominant language
- JavaScript
- Stars
- 104
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from scripting/reallysimple
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
scripting/reallysimple#22 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
scripting/reallysimple#21 · 4 comments ·
-
Feed discovery tips Open
Difficulty 1/5 Under an hour Newbie friendliness 20/100
scripting/reallysimple#20 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
scripting/reallysimple#19 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
scripting/reallysimple#18 ·
All issues in scripting/reallysimple
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100