-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CDATA filtering options, new item addition functions, unit tests, bug fixes #38
base: master
Are you sure you want to change the base?
Conversation
…concat_items and replace_items. Associated unit tests
…. Adding test for XML escaping when no_cdata_fields is used
… by item() resulting in inconsistencies like missing category field. Added test for this issue
…ply-for-new-pr Conflicts: lib/index.js test/rss.test.js
package.json
Outdated
@@ -57,10 +58,10 @@ | |||
"dependencies": { | |||
"folderify": "^0.6.0", | |||
"mime-types": "^2.0.3", | |||
"mime": "^1.2.11", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mime-types
should be good enough
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I clone (or rm -rf node_modules
), npm i
, and npm test
, I get an error for missing mime module unless mime
is in package.json
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see above :)
This is ready for review. |
(bump) |
@dylang, Is there any more info, documentation, or testing you need from me for this PR? |
Sorry for taking so long with this. I'll try to get to it later this week. |
Not a problem. Just wanted to make sure you weren't waiting for something from me. |
The cdata work looks good. I don't like the generic The I think a better API would be something like |
@dylang Your function rename suggestions are fine. Better to change them now than have a legacy support issue. |
To clarify, should |
Updating function names, docs, and unit tests as per discussion
@dylang, my latest commit changes the names of the extra functions and adds a unit test for |
@dylang, How are we going on this? |
@dylang... Any progress on this? |
@dylang, I've released the |
It seems like the Travis failure is related to npm3. This env has an npm config of
|
close/open to trigger Travis |
Any movement on this? Would love to see it get merged |
examples/simple.js
This PR supercedes #37, which has some relevant discussion.
This PR is similar to existing PR #28, but allows for finer control over what fields can be skipped for CDATA wrapping.