Repository navigation
fix(gitlab): Require group path in setup form - #128734
Open
jackeddisciple wants to merge 1 commit into
Open
jackeddisciple wants to merge 1 commit into
jackeddisciple wants to merge 1 commit into
Conversation
The backend rejects a blank group since getsentry#126385 but the form still said to leave it empty. Validate it in the form and fix the hint.
github-actions
Bot
added
the
Scope: Frontend
This branch has not been deployed
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.
Since #126385 the backend requires a GitLab group path, but the setup form still treated it as optional and the hint said "Leave empty to integrate all accessible projects". Leaving it blank only failed after the server came back with a 400.
The group path is now a required field, so a blank value gets caught in the form before anything is sent. The hint now explains that groups without a shared parent each need their own installation.
I went with fixing the form instead of allowing installs without a group, since that would undo #126385.
Fixes #128592
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.