Deprecate ldapFilter argument in createProject mutation #3364
Conversation
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
josephsnyder
approved these changes
Jan 13, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The
createProject()mutation was initially envisioned as a way to create projects while setting all optional fields at the same time, similar to the legacy create/edit project endpoint. In hindsight, this was a poor idea because it makes managing default values vs nulls vs user-defined values significantly more difficult. This PR deprecates the only non-essential field currently in thecreateProject()mutation in favor of a new approach where only a minimal subset of fields can be specified via this mutation. A separateupdateProject()allowing updates of individual fields will follow soon.