Skip to content
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

Improve jsonstringify and stringify operators docs: part 2 #7748

Conversation

mateuszwilczek
Copy link
Contributor

@mateuszwilczek mateuszwilczek commented Sep 21, 2023

Relevant discussion: https://talk.tiddlywiki.org/t/are-stringify-and-jsonstringify-operators-duplicates/7760
My previous PR about this: #7650

I'm reworking the docs of these two operators to make their similarities and differences more clear.

@vercel
Copy link

vercel bot commented Sep 21, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
tiddlywiki5 ✅ Ready (Inspect) Visit Preview Sep 22, 2023 0:31am

@Jermolene
Copy link
Owner

Looks good thanks @mateuszwilczek

<<.from-version "5.1.23">> If the suffix `rawunicode` is present, Unicode characters above 0x80 (such as ß, ä, ñ or 🎄) will be passed through unchanged. Without the suffix, they will be substituted with `\u` codes, which was the default behavior before 5.1.23.

<<.note """Characters outside the Basic Multilingual Plane, such as 🎄 and other emojis, will be encoded as a UTF-16 surrogate pair, i.e. with two `\u` sequences.""">>
<<.from-version "5.1.23">> If the suffix `rawunicode` is present, Unicode characters above 0x80 (such as ß, ä, ñ or 🎄) will be passed through unchanged. Without the suffix, they will be substituted with `\u` codes, which was the default behavior before 5.1.23. Characters outside the Basic Multilingual Plane, such as 🎄 and other emojis, will be encoded as a UTF-16 surrogate pair, i.e. with two `\u` sequences.
Copy link
Contributor

@CrossEye CrossEye Sep 22, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No critique here, just a question for the core team. How long do we keep these "New in 5.1.23" annotations around? There's been the entire 5.2.x train as well as 5.3.0 and 5.3.1, and this would likely appear in 5.3.2. Is there some official shelf-life?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question! When we introduced the version tags, I was indeed thinking that we'd have some sort of statute of limitations where we'd drop the older ones. We could do it crudely by searching and replacing in an editor, but I'd prefer to update the macro so that it parses the version number and doesn't produce any output if the version is less than some threshold.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll take a look into it, together with some other documentation-macro related edits I had in mind. Would a threshold of >= 5.2 be reasonable? That is, everything below 5.2 will be hidden?

@mateuszwilczek mateuszwilczek marked this pull request as ready for review September 22, 2023 13:44
@mateuszwilczek
Copy link
Contributor Author

I think the docs of the two operators in question are ready for merging now, they are more accurate and clear than before. Thanks to all that helped along the way!

@mateuszwilczek
Copy link
Contributor Author

@Jermolene this docs update is ready for merging (it's unrelated to v5.3.2). I have figured out the differences between the operators and documented them more clearly. I have just discovered that this PR is still hanging about.

@Jermolene
Copy link
Owner

Thank you @mateuszwilczek apologies for the delay.

@Jermolene Jermolene merged commit b08281a into Jermolene:tiddlywiki-com Nov 29, 2023
4 checks passed
munnox pushed a commit to munnox/TiddlyWiki5 that referenced this pull request Dec 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants