-
Notifications
You must be signed in to change notification settings - Fork 13
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
[DEV-13852] Refactoring - Allow custom rendering of placeholders #574
Merged
kudlajz
merged 12 commits into
main
from
feature/dev-13852-refactor-gallerybookmarkplaceholderelement
Nov 8, 2024
+313
−1,093
Merged
Changes from 2 commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
124a27d
Allow fully custom rendering of placeholders
kudlajz ae7cfc7
Revert to native placeholder if different node is selected
kudlajz 8b0ba09
Refactor StoryBookmarkPlaceholderElement to support custom rendering
kudlajz dae2851
Refactor StoryEmbedPlaceholderElement to support custom rendering
kudlajz 3d40957
Refactor ContactPlaceholderElement to support custom rendering
kudlajz db0237f
Tweak previously refactored placeholders to activate on mount
kudlajz 39d584b
Refactor InlinePlaceholderElement to support custom rendering
kudlajz 2bf5016
Provide onRemove conditionally based on the removable prop
kudlajz 3fe9f38
Specify element prop correctly
kudlajz 7d5d558
Refactor CoveragePlaceholderElement to support custom rendering (WIP)
kudlajz 09b291a
Bring back onCreateCoverage and reset to default placeholder when dra…
kudlajz 0df51e0
Bring back event when story bookmark placeholder is submitted
kudlajz 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 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 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 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 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 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.
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.
I am still wondering if it's a good idea to have this half-approach where the "initial" placeholder UI is rendered by the editor, but then the subsequent UI is custom rendered.
I think ideally it would be nice if we could render the whole placeholder outside of the editor (i.e. rendered via
renderPlaceholder
function) but this would also mean that we would need to implement drag & drop functionality and other things (loading states, placeholder management etc.), so I wasn't sure if we should do it now or at all.EDIT: We probably don't need to worry about placeholder management outside of the editor. It would still be internally managed by the editor as needed when using the respective callbacks.
The advantage of this "headless" approach is that we would have a complete control over the UI of the placeholders within the app and it will also allow other developers to bring their own UI (currently we force the placeholders to look the way they do, which I don't think is great).
Just wanted to hear your thoughts and opinions before I do the work, in case you don't think it's a good idea.
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.
I generally dislike how these extensions are structured with the code split between the app repo and the editor repo. Making the extension hard-to-use outside of the Prezly app. But hey! One step at a time! :)
With this refactoring I can definitely see that things become less complicated. And even though the code splitting issue is still there, it is a great improvement 👍