Ability to parse custom fields in rss that are not part of the spec #177
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Will add more test cases. |
sjawaji
force-pushed
the
master
branch
2 times, most recently
from
e9cb6b7 to
5b3db4e
Compare
|
@mmcdole - Added additional test cases. Are you happy to merge this? |
|
@mmcdole - possible to merge? The feature is urgently needed for me. |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have a requirement to parse elements that are not part of the standard spec. Noticed someone also recently raised this as part of the issue #174
Raising this pull request in case this will be helpful for others.