Support for v0.5
phemartin opened this issue · 10 comments
Is there going to be an upgrade to slate v0.5? Really hoping so. Cheers
@phelipe3 still unclear to me how stable 0.5 is. Seems like Ian is rapidly iterating on it.
I agree. Seams to be more stable nowadays. Any update?
My current setup really depends on this plugin so I'll be waiting for it. I can also help with the move as well. :)
@phelipe3 if you have the time, maybe make the PR? How big of a job do you reckon it is?
I'm looking at this in the coming days as I find time; does anyone happen to know of other mature plugins that have migrated to the new API? It would be helpful to use them as examples when I restructure the code.
@mmdonaldson I feel like I'm (currently) not that great of a programmer to issue a PM from scratch, but I definitely can help.
@jasonphillips The best plugin library I'am aware of is slate-plugins-next. (https://slate-plugins-next.netlify.com)
@phelipe3
Thanks, slate-plugins-next looks very well structured, I can use that as a clean reference.
Update: I'm still a bit torn as to how best to proceed with this library, given the discussion here:
slate-plugins-next is a smart approach, but builds its own custom plugins logic on top of slate, and I prefer ideally to have slate's core as my only assumption here. So I could either follow that secondary plugins approach--and wed this library to a strategy that is one step removed from slate, and might break since it's not part of slate's internal assumptions--or turn this library into a set of smaller components that you hook into your slate instance somewhat manually, since the concept of a single "plugin" enclosing many changes (schema, key listeners, etc) is no longer part of slate's design.
@jasonphillips what are you leaning towards? 0.5 fixes some long standing formatting bugs (worth upgrading for) and we also depend on slate-deep-table
FYI we are beginning the upgrade this week
Is this already supported yet?