Fix install script PATH activation after curl install#35
Merged
Conversation
… for better PATH management, and improve README instructions for setup. The install scripts now auto-configure the user's PATH and provide clearer next steps after installation.
…ted printf statements to use consistent syntax for better readability and maintainability.
…string interpolation for improved clarity in user instructions.
paulius-krutkis-dcd
changed the title
ChinchillaLover9000
approved these changes
Jun 16, 2026
domantas-jurkus-dcd
approved these changes
Jun 17, 2026
* Fix remaining critical CLI audit items - Object/array schema params now register as --flag <json> with a JSON-parsing argParser; invalid JSON is a usage error - Derive binary PNG output context from the built body so generated commands (universal --headless png) write a PNG, not base64 text - Map syscall-coded network failures (ENOTFOUND, ECONNREFUSED, ...) in the cause chain to exit 7 and render the cause - setup now rejects as a usage error on EOF/closed stdin instead of exiting 0 having saved nothing; handle TTY EOF and Ctrl+D - Add offline README docs regression test validating documented commands and flags against the command tree built from BundledSchema * Skip parse/markdown defaults for headless png screenshots Manual end-to-end testing surfaced that generated commands routed PNG output correctly but applyRequestDefaults still injected markdown:true, so the API returned markdown instead of a screenshot and PNG extraction failed. Skip the defaults when headless is png so universal --headless png writes a real PNG, matching the curated screenshot command. * Refactor CLI error handling by introducing CliUsageError class - Moved CliUsageError definition to a new file for better organization. - Updated imports across multiple files to reference the new location of CliUsageError. - Added tests for CliUsageError to ensure proper functionality and error message handling.
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
3 participants
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.
Summary
source/export PATHstep and use the full binary path for the setup prompt and get-started examplessetxguidance withSetEnvironmentVariable; bump version to 0.1.7Test plan
docs/install.shwith a read-only global npm prefix; verify profile is updated and activation steps are printedsetxand the restart-terminal message appears