Skip to content

fix: add correct HTML parsing #273

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

Merged
merged 8 commits into from
Jul 23, 2025
Merged

fix: add correct HTML parsing #273

merged 8 commits into from
Jul 23, 2025

Conversation

orama254
Copy link
Contributor

Added rehypeRaw to help with parsing the raw HTML inside the markdown files since markdown-it and react-markdown escapes HTML tags to prevent Cross-SIte Scripting.

This pull request resolves #261 and #267

Added rehypeRaw to help with parsing the raw HTML inside the markdown files since markdown-it and react-markdown escapes HTML tags to prevent Cross-SIte Scripting.
Copy link

netlify bot commented Jul 18, 2025

Deploy Preview for startling-capybara-2231ea ready!

Name Link
🔨 Latest commit 593afe7
🔍 Latest deploy log https://app.netlify.com/projects/startling-capybara-2231ea/deploys/687e57a5b745b70008d2d006
😎 Deploy Preview https://deploy-preview-273--startling-capybara-2231ea.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@pavlenex
Copy link
Collaborator

Hey @orama254 thanks for the PR, it seems you've addressed all, but this one which is still not fixed
Screenshot 2025-07-19 at 12 10 31

@orama254
Copy link
Contributor Author

orama254 commented Jul 19, 2025

Hey @pavlenex,

I noticed this while implementing the fix. There's a small blocker on how to access the spec files directly because I observed they were committed as submodules(referencing a remote repository HERE). There's a way that the markdown files on the sv2-spec are rendered that needs to be tweaked in order to give the correctly rendered information.

I have a strategy that would resolve this but I wanted to seek clarity on whether I can proceed with tweaking the remote reference to the spec files inside this pull request or on a separate pull request inside the remote repository. If option 1 is ok I'll have to make a separate pull request on the remote repository

It's some exciting git stuff behind the scene and I'm up for the task as I have already mapped out the whole procedure based on carefully analyzing how both repositories work.

Let me know.

@pavlenex
Copy link
Collaborator

@orama254 I don't understand what your approach is, you can try to do it in this PR.

orama254 added 6 commits July 19, 2025 11:32
Add submodule reference for docs edit
Revert back to the original submodule reference after debugging
Add the ability for a contributor to view build changes locally
rereference original submodule after finishing with the debugging.
@orama254
Copy link
Contributor Author

@pavlenex I just realized I was overestimating the magnitude of the task!

It was a simple fix on the global css file. My previous approach was assuming that it was how the markdown files were being converted from markdown to HTML.

Turns out the elements were just hidden!

I've addressed the pending changes.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Can you explained why changes in this file?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Can you explained why changes in this file?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Can you explained why changes in this file?

@pavlenex pavlenex linked an issue Jul 21, 2025 that may be closed by this pull request
revert to the initial repo state for the generated files and the reference commit for the submodules file. NOTE: add a git ignore file for the app/src/data folder to avoid json regeneration commits in future
@pavlenex pavlenex merged commit 69d4cd6 into stratum-mining:main Jul 23, 2025
4 checks passed
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.

embedded html not properly rendered for spec page Specs formatting on Protocol Security
2 participants