Repository navigation
docs(readme): describe the 0.11 CLI warning output and diagnostics of calls - #105
Merged
Merged
Conversation
|
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
cssforge | 6a7bbc1 | Commit Preview URL Branch Preview URL |
Nov 21 2026, 02:42 PM |
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
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.
The README still said that the CLI prints each warning to stderr as
cssforge: warning: <message>. The 0.11 CLI printswarning <path>: <message>.buildandcheckprint it on stdout after their output.generateprints it on stderr, so that stdout has only the generated content. JSON output gives the warnings asdiagnostics.The capabilities section also did not say that a call prints nothing. It now says that the warnings are in
result.value.diagnosticsand that the caller reports them, with an example.I ran
cssforge check,buildandgenerate --humanon a config with a 900ms motion duration, and the output matches the new text.moon run cssforge:readme-checkpasses. No changeset: only the README changes.