feat: references to klipper configuration #1363
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
if extension added to the editor instanze it creates for every "class" a block widget above with a link to the klipper ref TODO: - change to block widget - automatic generation: requires syntax tree - styling
|
FYI: I merged the other PR (#1200) to have a better syntax highlighting until this PR is finished. |
|
@forgodtosave any updates here? |
|
I am closing this PR because no response. Please create a new (up-to-date) PR if you want to continue working on this feature. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds a feature in the editor which adds links to the klipper configuration reference. It will place over each block of code (e.g. [printer]) a codemirror block widget containing a link to the corresponding configuration reference.
Related Tickets & Documents
Fixes #1320
code widget decoration example
Mobile & Desktop Screenshots/Recordings
[optional] Are there any post-deployment tasks we need to perform?
TODOS