Merged
Conversation
The identity response shows slug with a leading slash (e.g., "/897362094") but the CLI expects just the numeric value. Added explicit guidance to prevent users from copying the slug verbatim and getting network errors.
waynemsmith
added a commit
to Concurrent-Systems/fizzy-cli
that referenced
this pull request
Mar 28, 2026
Closes basecamp#9 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
"slug": "/897362094"→ use897362094Users copying the slug directly from
fizzy identity showwere getting network errors because the leading slash caused malformed URLs.Test plan
bundle exec rake test- all 103 tests pass