Hiero | Global: editorial with folder path#5829
Conversation
…nto feature/OP-7190_Use-folder-path-as-identifier-in-editorial
- some minor typos fixes - modules sorting
- refactor labels
|
Task linked: OP-7190 Use folder path as identifier in editorial |
|
Task linked: OP-7176 Use folder path as unique identifier |
…nto feature/OP-7190_Use-folder-path-as-identifier-in-editorial
|
Publishing is crashing on Logging: line 65: |
|
Here is also strange thing happening on server. Althought the publishing was not successfull from my previous post here following was created on server. But as you can see the name of folder is now path and not simply |
|
issue with hierarchy from comments #5829 (comment) and #5829 (comment) |
Co-authored-by: Jakub Trllo <43494761+iLLiCiTiT@users.noreply.github.com>
…nto feature/OP-7190_Use-folder-path-as-identifier-in-editorial
antirotor
left a comment
There was a problem hiding this comment.
didn't tested, otherwise it looks good
| self._convert_to_tag_data() | ||
| tag_hierarchy_data = self._convert_to_tag_data() | ||
|
|
||
| self.tag_data.update(tag_hierarchy_data) |
There was a problem hiding this comment.
just a naive note about self.tag_data - since it is updated with the content of tag_hierarchy_data, shouldn't it be used late on instead of it? Also, this whole method is returning tag_hierarchy_data but the instance property tag_data already has all of it but is different?
…nto feature/OP-7190_Use-folder-path-as-identifier-in-editorial
…nto feature/OP-7190_Use-folder-path-as-identifier-in-editorial
…nto feature/OP-7190_Use-folder-path-as-identifier-in-editorial
iLLiCiTiT
left a comment
There was a problem hiding this comment.
One suggestion, otherwise code looks ok. But I don't know how to test.
|
Let's merge this and do a final pass in the target branch |
477bc61
into
feature/OP-7176_Use-folder-path-as-unique-identifier


Changelog Description
Support for folder path unique identifier in editorial and particularly in Hiero. This allows multiple shots with the same names in different sequences to be accepted during publishing.
Additional info
Based on #5817 and expands it towards Editorial publishing.
Testing notes: