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

Organize markdown parser usage #49

Closed
cloverich opened this issue Sep 20, 2021 · 2 comments
Closed

Organize markdown parser usage #49

cloverich opened this issue Sep 20, 2021 · 2 comments

Comments

@cloverich
Copy link
Owner

Remark / Unified parsers are created and used in a few different places in the application. This will likely lead to buggy behavior in one form or another if their usages drift or it becomes unclear when different parsers are being used.

  • Review and consolidate all markdown usage; document if necessary
  • Review whether 3rd party libraries like remark-slate-transformer will be impacted, or whether it should be incorporated into the codebase directly
  • Upgrade all remark dependencies (the ecosystem has made a few major changes, e.g. micromark)
@cloverich
Copy link
Owner Author

consolidated: c53112b

Likely should upgrade library now, and investigate helping out with since I currently have all the context.

cloverich added a commit that referenced this issue Oct 15, 2021
- add @udecode/plate library and migrate various custom slate code to it (closes #68 )
- add toolbar and various wysiwyg shortcuts
- add  fancy code blocks
- add list support (through shortcuts only)
- remove markdown support
- add a test for the parse step, even though i cannot get it to run :|
- add a top-level ErrorBoundary
- update remark related dependencies
- organize and refactor remark usage post upgrade #49 
- clean-out a few other unused dependencies #38 
- move rebuild from postinstall to specific command (avoids rebuilding every dependency change)
@cloverich
Copy link
Owner Author

4c8d54d

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

No branches or pull requests

1 participant