Refactor users.cc RSS generation into functions#129
Open
wandernauta wants to merge 2 commits into
Open
Conversation
This splits the different feed-producing functions in users.cc so that they no longer each individually interact with pugixml directly. The new code always picks the most recent pubDate (in practie: "bijgewerkt") as the channel's lastBuildDate. Before, some functions would pick some earlier date, for example the most recent "datum". Otherwise, the output should be byte-for-byte identical. Some duplication still remains between the different feed-producing functions, since at the moment they all happen to generate feeds containing Documents; this can be further reduced if desired.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
This splits the different feed-producing functions in users.cc so that they no longer each individually interact with pugixml directly.
The new code always picks the most recent pubDate (in practice: "Document.bijgewerkt") as the channel's lastBuildDate. Before, some functions would pick some earlier date, for example the most recent "datum", or the epoch. Otherwise, the output should be byte-for-byte identical.
Some duplication still remains between the different feed-producing functions, since at the moment they all happen to generate feeds containing Documents; this can be further reduced if desired.