Repository navigation
test(completion): cover predictors with envtest and honor --context in the namespace predictor #534
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
jcogilvie
wants to merge
5
commits into
crossplane:main
Choose a base branch
from
jcogilvie:jco-completion-integration
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
6cab8c9
test(completion): pin the kube predictors against envtest
jcogilvie c6ffa8e
refactor(completion): build the predictors' clients on kube.RESTConfig
jcogilvie f19ed27
fix(completion): honor --context when predicting namespaces
jcogilvie 8fc7b3c
fix(completion): don't panic when --context or --namespace is the las…
jcogilvie 602ccb7
Parse attached --context and --namespace values in completion
jcogilvie File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Support attached context values in namespace completion.
Thank you for adding context selection. The CLI accepts
--context=adminand-cadmin, butparseContextmatches neither form. If the current context is unreachable,namespacePredictortherefore returns no results for--context=admin --namespace team, although the command selectsadmin. Please parse these forms and cover them in an integration case. (raw.githubusercontent.com)As per path instructions, “Review CLI commands for proper flag handling, help text, and error messages.”
Source: Path instructions
Use the final context flag for namespace completion.
For
--context unreachable --context admin --namespace team, Kong uses the final context flag.parseContextstops at the first flag instead, so namespace completion queriesunreachableand returns no results. Please match the CLI’s flag precedence and cover repeated context flags. (raw.githubusercontent.com)As per path instructions, “Review CLI commands for proper flag handling, help text, and error messages.”
Source: Path instructions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done in 602ccb7. I checked kong's parsing first: it splits a long flag on
=and takes everything after a short flag's letter as its value, so--context=adminand-cadminare both valid.parseNamespaceOverridehad the same gap (--namespace=team,-nteam), so both now share oneparseFlagValuehelper covering all four forms.New cases:
LongAttachedandShortAttachedinTestParseContextandTestParseNamespaceOverride, plus integration casesAttachedContextOverride(--context=admin --namespace team) andAttachedShortContextOverride(-cadmin --namespace team) with an unreachable current context. All six failed before the change.Reply posted by Claude Code on behalf of the PR author.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Analysis chain
Script executed:
Length of output: 10086
@jcogilvieThanks for the fix and the added tests. I checked commit602ccb75: the attached forms and their test cases are present. I did not run the tests.One concern in this thread remains:
parseFlagValuestill returns the first context flag (completion.go, Line 244). For repeated flags, completion can therefore use a different context from the command. Could you update the precedence and add a repeated-context test?If you found this review helpful, would you consider giving us a shout-out on X?
Thank you for using CodeRabbit!
You are interacting with an AI system.