forked from Sofie-Automation/sofie-core
-
Notifications
You must be signed in to change notification settings - Fork 1
Refactor Segment/Part properties to be a property instead of an operation #38
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
Merged
mint-dewit
merged 5 commits into
feat/ui-useredit-panel
from
chore/ui-useredit-properties
Dec 5, 2024
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -66,3 +66,48 @@ export interface CoreUserEditingDefinitionSourceLayerForm { | |
| value: Record<string, any> | ||
| } | ||
| } | ||
|
|
||
| export interface CoreUserEditingProperties { | ||
| /** | ||
| * These properties are dependent on the (primary) piece type, the user will get the option | ||
| * to select the type of piece (from the SourceLayerTypes i.e. Camera or Split etc.) and then | ||
| * be presented the corresponding form | ||
| * | ||
| * example: | ||
| * { | ||
| * schema: { | ||
| * camera: '{ "type": "object", "properties": { "input": { "type": "number" } } }', | ||
| * split: '{ "type": "object", ... }', | ||
| * }, | ||
| * currentValue: { | ||
| * type: 'camera', | ||
| * value: { | ||
| * input: 3 | ||
| * }, | ||
| * } | ||
| * } | ||
| */ | ||
| pieceTypeProperties?: { | ||
| schema: Record<string, UserEditingSourceLayer> | ||
| currentValue: { type: string; value: Record<string, any> } | ||
| } | ||
|
|
||
| /** | ||
| * These are properties that are available to edit regardless of the piece type, examples | ||
| * could be whether it an element is locked from NRCS updates | ||
| * | ||
| * if you do not want the piece type to be changed, then use only this field. | ||
| */ | ||
| globalProperties?: { schema: JSONBlob<JSONSchema>; currentValue: Record<string, any> } | ||
|
|
||
| /** | ||
| * A list of id's of operations to be exposed on the properties panel as buttons. These operations | ||
| * must be available on the element | ||
| * | ||
| * note - perhaps these should have their own full definitions? | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. should this note be handled in this PR? As the blueprint version of this interface has the full definition for these, it would make sense to keep that here too. It looks like the ui is expecting them to be the full definitions too |
||
| */ | ||
| operations?: CoreUserEditingDefinitionAction[] | ||
|
|
||
| /** Translation namespaces to use when rendering this form */ | ||
| translationNamespaces: string[] | ||
| } | ||
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Do we still want/need the
CoreUserEditingDefinitionSourceLayerFormand similar types?I don't mind if they stay, just want to ask the question