When will the 1.0 version be released, Is there an out of the box editor based on slate？

[gland2015]

Problem
A clear and concise description of what the problem is. (Eg. I'm always frustrated when [...])
When will the 1.0 version be released
Solution
A clear and concise description of what you want to happen.

Alternatives
A clear and concise description of any alternative solutions or features you've considered.

Context
Add any other context about the problem here. (The fastest way to have an issue fixed is to create a pull request with working, tested code and we'll help merge it. Slate is solving a pretty complex problem, and we can't do it without active contributors, so thank you so much for your help!)

[dylans]

The closest I have to an answer is in #4540 (comment)

[jemc]

That comment was about a year ago now, so I'm curious if/how the landscape has changed.

The items written in that comment were:

• slate-react needs more flexibility for overriding smaller chunks of the API (for example, there's the currently open issue to make insertData, setFragment, and copy/paste easier to extend without needing to override completely)
• slate-react has minimal tests at best
• general cross-browser quirks need better tests
• making the TypeScript approach a bit better ( revisit and land a refactor based on
  Generic typescript #4177 )
• another wave of reviewing and stabilizing the API

Are there issue tickets for those items? Perhaps they could be linked to a 1.0 milestone in GitHub?

People who are awaiting the 1.0 release could potentially help collaborate on getting some of these items across the finish line if we could enumerate exactly what's needed and track them in issue tickets.

Any of the core contributors want to help give clarity on this?

[dylans]

That comment was about a year ago now, so I'm curious if/how the landscape has changed.

The items written in that comment were:

• slate-react needs more flexibility for overriding smaller chunks of the API (for example, there's the currently open issue to make insertData, setFragment, and copy/paste easier to extend without needing to override completely)
• slate-react has minimal tests at best
• general cross-browser quirks need better tests
• making the TypeScript approach a bit better ( revisit and land a refactor based on
  Generic typescript #4177 )
• another wave of reviewing and stabilizing the API

Are there issue tickets for those items? Perhaps they could be linked to a 1.0 milestone in GitHub?

People who are awaiting the 1.0 release could potentially help collaborate on getting some of these items across the finish line if we could enumerate exactly what's needed and track them in issue tickets.

Any of the core contributors want to help give clarity on this?

If you look at the past year, you’ll observe that we release quite regularly, but there’s still been a fair bit of churn. I don’t think it’s as simple as “address this short list, call it 1.0”, but if I was to try, I’d say it’s some mix of the following:

• A reliable automated test suite (we have a few open PRs all taking a different approach with respect to tooling)
• Addressing some of the more critical open issues (some on performance, boundaries/edges, copy/paste, etc.)
• Looking at areas of the API that should be more extensible/replaceable
• Switch to React 18+ (I’m not confident that fully supporting React 18 won’t break users of older React versions, even with their shins for new hooks introduced)
• Support for new copy/paste API (Safari will probably be the first to require it)

[jordanpapaleo]

Hi @dylans :) How much of the churn is specific to slate v plate?

[Nantris]

Switch to React 18+ (I’m not confident that fully supporting React 18 won’t break users of older React versions, even with their shins for new hooks introduced)

@dylans I don't know if it's relevant, but we're way back on 0.45.x, using React 18.1 without any problems.