Repository navigation
BUG: NeosCon schedule api: decoding special chars for topic title, description, speaker summary - #724
Merged
Merged
Conversation
…cription, speaker name & speaker, summary & event name
…eaker & talk description
Member
|
Thank you @minedesign-jl . From my POV an API shouldn't html encode it's values, so the APU could get used also in a non-HTML context. Rather should the encoding happen on the consuming side. Where did you noticed the wrong encoding? In the NeosCon App? |
Collaborator
Author
|
@dlubitz I am trying to decode, not encode. |
Member
|
Ahh, sorry. I misread the PR. 👍 |
dlubitz
approved these changes
May 25, 2026
Sebobo
reviewed
May 26, 2026
Sebobo
approved these changes
May 26, 2026
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.

Schedule api updated to decode html special characters so a readable string is returned.
goal:
&instead of& should always be