Orgs custom fields #269
Merged
Orgs custom fields #269
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
Contributor
Author
|
Main changes:
The last one is needed, as custom fields can't write to non-existent orgs, so we need to create them first (e.g. by setting them from custom fields fro teams). Not sure if I like this solution, but didn't come up with anything better. Maybe we can just create from override if it's missing, but it would have most of the values really strange. |
|
Playwright tests screens
|
kunyavskiy
force-pushed
the
orgs-custom-fields
branch
from
cd15247 to
fdd52a1
Compare
|
Playwright tests screens
|
Also support some clics fields as explicit ones.
kunyavskiy
force-pushed
the
orgs-custom-fields
branch
from
fdd52a1 to
0a3b58f
Compare
|
Playwright tests screens
|
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.
No description provided.