Custom link names #82
Merged
+117
−49
Conversation
This file contains 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
Minkiu
reviewed
Jan 10, 2024
iLLiCiTiT
approved these changes
Jan 11, 2024
Minkiu
reviewed
Jan 11, 2024
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.
link table is changed to contain a custom
namefield.The name is nullable and it may be used to use an integration-specific identifier. Links of the same type no longer need to be unique.
On the database level, the following has changed:
link_nametolink_typenamecolumnauthorfromdatato its own columnlink_unique_IDXAPI-wise, this PR should be 100% backward compatible, but
linkfield in[POST] /api/{project_name}/linksis now deprecated. Instead, please uselink_type(for now, both may be used).Graphql and rest both expose new optional
namefield.Testing
This PR is now in
ayon:experimentalimage. In order to migrate existing projects to the new schema, the container must start (reloading only won't trigger the migration script).If you restore an older project, restart the container afterward, so it is converted as well - projects with older schemas should work, only links will be broken.
link types weren't changed in any way.