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
✨ Enhancement: Review the implementation of the JSON editor to better management of state/style #560
Comments
Shall I continue working on this @benjagm as I have the idea of code components |
Heyy @benjagm Can I work on this?? |
I totally agree with you @benjagm to improve or extend the code editor, however, we can go with next-mdx-remote npm package that can handle rendering of mdx, formatting of any valid language or syntax on the client side. It provides a great User and Developer experience. very nicely go with NextJs as well :) |
Hello @akkshitgupta I tried using that but somehow it wasn't supporting some styles which needed to be applied to the rendered code. |
This is a big feature to be developed. Are you sure @Adity20 ? |
Maybe me and @AdityaSingh-02 can work together on this one if he is okay as he also worked on one issue related to this. |
It will be fine for me if at least to make an analysis and a proposal, even thought you don't implement it |
Okay, then I'll make a plan and will present it to you soon. |
Yup we can work together on this @Adity20 |
Just checking back in on this issue. Is anyone actively working to resolve this issue? |
Yes |
Is your feature request related to a problem? Please describe
Related: #417
As of now we are using 2 different code editors: 1 JSON and JSON Schema (json editor) and another for the rest of languages.
This is providing an inconsistent experience in terms of formatting but also in terms of features. Ideally we'll use one single document that provides:
Describe the solution you'd like
Use or extend a code editor or improve the current implementation using 2 different editors.
We'd like to have a feature to highlight specific lines of code (Like git diff)
Describe alternatives you've considered
No response
Additional context
No response
Are you working on this?
No
The text was updated successfully, but these errors were encountered: