feat: improve post body rendering on Web UI #106
Merged
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
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.
Previously, the "Rendered" view was parsed from the raw XML feed on the front-end. The logic on determining which field to show as posts' bodies is arbitrary. Since #100, I changed the logic to recognize more post body types. However, such change was not reflected on the Web UI. This PR updates the Web UI to show the expected body content.
Besides, I made some visual tweaks to the Rendered view to show more information including post's publication date, feed's description, etc.
In addition, The status bar will now show the number of posts on successful fetches.