Thunder App

2811 readers

1 users here now

An open-source, cross-platform Lemmy client for iOS and Android.

This community is intended to discuss features and feature suggestions for Thunder; as well as friendly, respectful talks about Lemmy in general.

Please use the GitHub repository linked below to submit bug reports, so keeping track of them is easier, and make sure to search first if you already can find an issue for your report.

If there are any developers who would like to contribute, feel free to reach out on GitHub!

General Links
Website: Link
GitHub Repository: Link
Matrix Space: Link

Android Releases
IzzyOnDroid: Link
Google Play: Link

iOS Releases
Apple App Store: Link
TestFlight Beta: Link

Related Communities
Nightly Community: Link

founded 1 year ago

MODERATORS

darklightxi@lemmy.world

poolitzer@lemmy.world

darklightxi@lemmy.ca

micahmo@programming.dev

Space after ::: in spoiler (programming.dev)

submitted 8 months ago by sukhmel@programming.dev to c/thunder_app@lemmy.world

3 comments fedilink hide all child comments

It seems that the web UI treats spoilers without a space after ::: the same as the regular ones, while Thunder ignores those as spoilers. It looks like the closing spoiler marker may be entered without whitespace but it consumes extra text after the spoiler, and overall acts weird

I can create an issue if that's needed, or this post may be referenced in an existing issue to be used as a test

no whitespace
Content



whitespace present
Content



one-liner no whitespace
Content

one-liner whitespace present 
Content

Extra text in the end

one-liner whitespace present Content


Second extra text

produces

no whitespace

Content

whitespace present

Content

one-liner no whitespace

Content

one-liner whitespace present

Content

Extra text in the end

one-liner whitespace present

Content

Second extra text

you are viewing a single comment's thread
view the rest of the comments

[–] darklightxi@lemmy.world 0 points 8 months ago (1 children)

Thanks for the feedback! It would be awesome if you could create a new GitHub issue on this so that it makes it easier to keep track of.

Just as you mentioned, there doesn't seem to be a definition for what correctly defines a spoiler tag in Lemmy, so it's a bit difficult to get all the edge cases right! I kept the parsing to be limited to what Lemmy UI produces when you press the spoiler tag (which adds a space after :::). This is also non-standard markdown which makes it particularly more difficult to implement 😅

For reference, this is what Lemmy UI generates as a template:

spoiler___

[–] sukhmel@programming.dev 2 points 8 months ago

I've filed an issue. I tried to be clear and concise but not sure if I did a good job at that.

All in all, it seems like there needs to be a post with all the possible combinations of weird stuff (e.g. using tabs as whitespace, not having closing ::: etc) and some interaction with lemmy-ui dev to understand if that cases are treated correctly by them and what is an intended way