Repository navigation
Compatibility: Moonraker on Snapmaker does not mean Klipper support - #50
Open
saucissefarciehumaine-prog wants to merge 1 commit into
Conversation
Closes TigerTag-Project#12. One sentence in two places, as the issue asks: a note under the matrix, and a paragraph on compatibility/klipper.md, saying the Snapmaker link happens to use Moonraker and that generic Klipper machines are not supported. The "groundwork exists" wording and the TODO are left as they are. i18n/fr mirrors updated, hashes current. check:docs, check:i18n and build green locally. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@saucissefarciehumaine-prog is attempting to deploy a commit to the Tiger-Project Team on Vercel. A member of the Team first needs to authorize it. |
This branch has not been deployed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #12. One subject — your issue — branched from current
main, not stacked on anything.What it does, exactly as the issue asks. One sentence in the matrix note and one on
compatibility/klipper.md, saying the Snapmaker link happens to use Moonraker and that generic Klipper machines are not supported:compatibility/README.md— a note directly under the matrix, before the RFID-sheets note, linking the Klipper page.compatibility/klipper.md— one paragraph right after the one that introduces the Moonraker groundwork: sharing the transport does not mean sharing the support.Left as it is. The "groundwork exists" wording, the status table and the
TODOon which Moonraker surface to target. The issue is about the conclusion a reader draws, not about the roadmap.Four files, both locales. Two existing pages and their
i18n/frmirrors, hashes refreshed. No new route, no sidebar entry.pnpm check:docs,check:i18nandbuildall green locally (131 pages, all internal links valid); both sentences are indist/in EN and FR.🤖 Generated with Claude Code