Skip to content

Added none to available response_types flag#142

Merged
mschaab-SA merged 1 commit intomasterfrom
feature/responseTypeNone
Jan 22, 2026
Merged

Added none to available response_types flag#142
mschaab-SA merged 1 commit intomasterfrom
feature/responseTypeNone

Conversation

@mschaab-SA
Copy link
Copy Markdown
Contributor

When testing flows using the flag --response_types none I noticed I was getting the following error

  ERROR   ResponseType[0] must be one of [code id_token token]

But if I didn't include the flag I got a selector which did have the respose type none available. This change just changes the validator on the flag so none is available without needing the tui

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes a validation inconsistency where the response type "none" was available in the TUI selector but rejected when using the --response-types CLI flag. The fix adds "none" to the list of valid response types in the struct field validation tag.

Changes:

  • Added "none" as a valid response type in the ClientConfig struct validation tag

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@mschaab-SA mschaab-SA merged commit b9af889 into master Jan 22, 2026
10 checks passed
@mschaab-SA mschaab-SA deleted the feature/responseTypeNone branch January 22, 2026 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants