0.6.0-alpha

[Bistard]

Description

• Rewrite EVERYTHING related to EditorWidget.
• Upgrade version from 0.5.2 to 0.6.0

Issue(s) Addressed:

• https://github.com/Bistard/nota/issues/222
• https://github.com/Bistard/nota/issues/234
• https://github.com/Bistard/nota/issues/236

Changes

Type of Changes: Bug fix / new feature / breaking change

Environment

1. Depends on marked library
2. Depends prosemirror-history library
3. Upgrade typescript from 5.4.2 to 5.6.3
4. Uninstall jsdom-global library, using jsdom directly in Mocha testing environment

UI

1. MacOS now supports its own styled window bar (macos-qa-bar)
2. Refactor: fully functional ActionBar (dev-action-bar)
3. Complete UI of ContextMenu (dev-context-menu)
   1. FileTree now supports ContextMenu
4. new service: OutlineSerfvice (dev-outline)
5. refactor service: NotificationService (dev-notification)
   1. With brand new UI.

Editor

1. Extensions
   1. EditorExtension (base class for editor-related extensions)
   2. Refactor: CommandExtension (Fully functional)
   3. New: AutoSaveExtension
   4. New: temporarily using prosemirror-history to support undo/redo
2. EditorModel
   1. Refactor: temporarily remove PieceTable and EditorViewModel. Use ProseEditorState as model by now.
   2. Improve: DocParser
   3. New: MarkdownSerializer
      1. Include tons of unit tests
3. EditorView
   1. Refactor: remove inheritance hierarchy (ReadableEditor, WritableEditor)
   2. with basically no good-looking UI styles.

Others

1. Event System: able to monitor memory leak for Emitter (using FinalizationRegistry)

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
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [x] Any dependent changes have been merged and published in downstream modules

Reviewers Checklist:

• [ ] Code follows project guidelines and clean code principles
• [ ] Tested on various resolutions and browsers
• [ ] Unit tests have been updated or added, if necessary
• [ ] Documentation has been updated