-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: fetching team_settings data from database and populating forms #3319
Conversation
5a52e40
to
0f171d6
Compare
779b520
to
f298693
Compare
f298693
to
f1c70fc
Compare
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.
The changes in this file (removed commas) don't match our linting style. Husky should be picking this up and fixing it as part of a pre-commit hook but this clearly isn't working right atm for your setup it seems. We can also look at checking this at the CI stage if we need to.
You can fix this file with pnpm lint:fix
PR Closed as overlapping changes became too tangled, changes have been moved to fresh branch: |
What does this PR do?
Continuing work on the
team_settings
implementation, this PR pulls in data from the database with a graphQL query and populates the corresponding form inputs.This PR also uses the update mutation, similar to
team_themes
to update the form fields and database.This PR aligns with a planx-core change where the requests and types for a Team were altered to incorporate the new
team_settings
table.Reference to the planx-core changes