-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add minimal workflow support #14
Conversation
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.
Just by reading the code, I don't understand the difference between WorkflowStatus.DRAFT and WorkflowState.draft.
Maybe use a Class with an init logic that can make the difference explicit? Or maybe a comment is enough.
Tried to clarify. What do you think? |
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.
Clearer since we don't have two drafts status/state anymore 👍 And it feels like more complexity is surfacing, which is probably a business thing on geonetwork's side...
2155ef9
to
7a706cd
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.
🧑🎨
On records with workflow enabled: - record has no draft (working copy) -> proceed - record has draft -> raise error This is to avoid the flaky draft implementation in Geonetwork, at least for now.
6e147b4
to
258c2d9
Compare
Fix #15
On records with workflow enabled:
This is to avoid the flaky draft implementation in Geonetwork, at least for now.