change `plugin.render` to `plugin.renderPortal`
See original GitHub issueOriginally I figured always rendering into a portal would be the easiest way to avoid having to deal with plugin render contention. But I’m just realizing that treating it as a HOC stack could work too, so we might end up with:
plugin.render
plugin.renderPortal
And the core plugin can actually just be the final occurrence of plugin.render
to render the actual editor logic itself!
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Plugin to modify page before it's rendered - WordPress.org
I am moving from PHNuke to WordPress. My site is a technical tutorial with several hundred pages. I have my own module that...
Read more >Portals - React
Portals provide a first-class way to render children into a DOM node that exists outside the DOM hierarchy of the parent component. ReactDOM....
Read more >How to create a rendering plug-in class | HCL Digital Experience
A rendering plug-in is a reusable class that you create to run a task at render time. It can be referenced within web...
Read more >Renderer Plugins - DokuWiki
Renderer plugins aka. pluggable renderers, allow to implement different rendering mechanisms for DokuWiki. DokuWiki parses Wiki syntax into ...
Read more >php - How to change which partial is rendered in OctoberCMS ...
By default, OctoberCMS plugin components render the partial default.htm . Is it possible to override which partial will be rendered?
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think there are cases where you don’t want
SlateNodePortal
, and you might want aSelectionPortal
instead, or just a portal that puts things at the top-left/right of the editor. I’ve got both of those cases currently in my setup.I’d rather just have less, because any of those solutions can be solved by a single
plugin.render
handler, since then you have full control over where to put the portal.Fixed in
0.18
!