### Description
This pull request updates the plain text conversion logic to better
handle spoilered text, ensuring that spoiler formatting is replaced with
`[Spoiler]` in plain text fallbacks as per
[MSC4454](https://github.com/matrix-org/matrix-spec-proposals/pull/4454).
**Spoiler handling improvements:**
- Spoilered text (delimited by `||`) is now replaced with `[Spoiler]` in
the plain text output, matching the MSC4454 specification.
#### Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
### AI disclosure:
- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
No AI involved
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
Migrates from eslint and prettier to oxlint and oxfmt + some rule
hardening and - some rules that don't exist in oxlint, but I decided it
probably wasn't worth running both in parallel just for a few rules.
Notably, got rid of many "as any"s and swapped to .toSorted() for safer
stuff and "type" in imports. Added comments to all the existing lint
issues (console logging and the alert for app updates) and the few
places "as any" was justified (test cases) and some message object
whatnots.
Also notably, fmt now takes a second or two, and linting now takes no
more than a few seconds. Yay!
Recommended vscode plugins, workflows, and configs should all be updated
assuming I didn't miss anything.
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
#### Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [x] Breaking change - breaking I guess since not all rules exist? I
don't really know exactly what I uh... didn't include.
- [ ] This change requires a documentation update
### Checklist:
- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
### AI disclosure:
- [x] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
I deployed a swarm of silly AIs to fix many of the simpler as any casts
and subsequent typechecks because there were hundreds and I'm not doing
that manually :p. I did review it, mostly just seamless swapping to the
correct cast type instead of as any, nothing particularly complicated.
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
This PR proposes the moving of embed settings to their own category
under General:
<img width="810" height="694" alt="image"
src="https://github.com/user-attachments/assets/972eec7b-1517-4c76-991c-c652cea6a3ab"
/>
Additionally it adds multiple embeds in one message:
<img width="1321" height="480" alt="image"
src="https://github.com/user-attachments/assets/59a6da99-e7a1-4740-a9d8-29b37a2ef8dc"
/>
Showing them all is however just a setting that may be turned off (it is
on by default) since the embeds respect the aspect ratio of the
thumbnail so a list of embeds may be uneven which might appear
unaesthetic to some, as per this example:
<img width="1294" height="751" alt="image"
src="https://github.com/user-attachments/assets/6b0b47ad-c6e7-427f-baea-0ecd4ba84527"
/>
Fixes #
#### Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
### Checklist:
- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [x] My changes generate no new warnings
### AI disclosure:
- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
My pathological avoiding anxiety has empowered me to create this instead
of doing a more important task.
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
This PR proposes styling the misc data (the fields from extended profile
that sable does not recognize) in a more robust form, with json
formatting, and tapping through the options in order to have a clear
visual differentiation between it and anything else.
(current view for an example from someone using a different client and
thus having different fields)
<img width="350" height="701" alt="image"
src="https://github.com/user-attachments/assets/996bbcef-f7cf-4bbb-8667-051181d72835"
/>
(proposed new view, with the badge key selected)
<img width="344" height="661" alt="image"
src="https://github.com/user-attachments/assets/09cb347d-d287-477b-9562-5854ab09905b"
/>
(proposed new view when selecting an item)
<img width="345" height="564" alt="image"
src="https://github.com/user-attachments/assets/e52d18af-ae60-4747-9fd6-eef086373fe1"
/>
<img width="345" height="653" alt="image"
src="https://github.com/user-attachments/assets/9252b65f-d8ea-4926-8793-1b9ddff99b0a"
/>
(proposed view when there is only one key, and showing it is selected)
<img width="346" height="573" alt="image"
src="https://github.com/user-attachments/assets/4003f601-ddf4-44e9-b05d-4c07a4015033"
/>
Fixes #
#### Type of change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [x] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
### AI disclosure:
- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
My partner's avocado gasped the implementation as its last breath before
rotting away
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
Fixes#646
Changed settings link behavior to use a query parameter marker instead,
this avoids hardcoding `app.sable.moe`, keeps links valid on non-Sable
clients, and lets self-hosted Sable instances recognize links copied
from other Sable instances without misclassifying arbitrary third-party
`/settings/...` URLs.
Example:
`https://client.example/settings/account?focus=display-name&moe.sable.client.action=settings`
Edit:
I've ended up expanding the scope of the PR. Thanks to some suggestions
from @dozro and also general QoL improvements.
- Settings link URLs now get rewritten when sent from the RoomInput by
turning bare settings URLs into markdown links, so they look better on
non-Sable clients.
- Example on non-Sable clients: [Settings > Emojis & Stickers > Select
Pack](http://localhost:8080/settings/emojis?focus=select-pack&moe.sable.client.action=settings)
- Raw markdown sent: `[Settings > Emojis & Stickers > Select
Pack](http://localhost:8080/settings/emojis?focus=select-pack&moe.sable.client.action=settings)`
- Hardened settings link detection to avoid misclassifying invalid or
malformed URLs as settings links.
- Added validation so a settings link only renders as a settings chip if
it points to a real shareable settings target that exists.
- Invalid or malformed settings-looking URLs now fall back to normal
links instead of rendering as settings chips or trying to open invalid
focus targets.
- Fixed a styling issue where the settings link chip was not vertically
aligned with surrounding text.
- Removed settings links from dynamic/user-driven rows, such as emoji
packs and similar targets that are not stable to share across clients or
instances.
Migration note:
- `settingsLinkBaseUrl` is no longer used and can be removed from
`config.json`.
#### Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [x] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
### AI disclosure:
- [x] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->