feat: entrypoint drafts in UI #569
Open
+253
−46
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
jkglasbrenner
added
the
blocked
hbooth
removed
the
blocked
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.
This PR implements drafts for entrypoints. To test, try to create/edit/delete a resource/new-draft/resource-draft, and verify these scenarios don't conflict with eachother.
Create/edit/delete normal entrypoint
Create new draft (click add, Save Draft button is on bottom left corner)
Edit/delete new draft (click new drafts tab, then follow usual workflow)
Create draft from resource (click hasDraft button, form will be populated with resource values)
Edit/delete draft from resource (select row, edit/delete buttons are now dropdowns that allow you to pick the resource or the resource draft)
Note: the queues/plugins may not display correctly because the backend sometimes returns them as an array of objects, and other times an array of ids. Will need to discuss if this should be fixed in the backend or frontend.