v3: roadmap to release

[layershifter]

This PR tracks work for Semantic UI React v3 🎉

Pre beta-0 ✅

• chore: replace ta-scripts with release-it

For beta-0 ✅

• All components support native ref forwarding feat: use React.forwardRef in all components #4233
• BREAKING CHANGE remove Ref component chore(Ref): remove component #4286
• BREAKING CHANGE remove Visibility component chore(Visibility): remove component #4257
• BREAKING CHANGE Input, Button & TextArea are forwarding refs to native elements
• BREAKING CHANGE Transition static props chore(TransitionGroup): use React.forwardRef() #4266

Post beta-0 ✅

• Document breaking changes docs: add migration guide to v3 #4431

For beta-2 ✅

• fix: remove usages of .defaultProps FormInput: Support for defaultProps will be removed [v3] #4426, see FormInput: Support for defaultProps will be removed [v3] #4426 (comment)
• chore: update typings, ensure that they support ref forwarding Improve typings [v3] #4432, see Improve typings [v3] #4432 (comment)
• Not working with next.js 13 server components #4433

For beta-3

• [v3.0.0-beta.2] Type Tab.Pane is missing #4457
• fix(Popup): fix ability to not hide popup on scroll #4490
• BREAKING CHANGE Event handling: remove eventStack
• test: validateTrigger should handle forwardRef
• chore: remove .displayName in production
• docs: update contributing guide
• docs: update Github templates
• docs: update introduction to remove AutoControlledComponent mentions
• docs: rename classname generators (currently they violate rules of hooks as their names start with use)
• chore: enable ESLint plugin for rules of hooks

For RC

• chore: integrate monosize
• chore: add bundle size fixtures for all components
• chore: remove dependency on lodash
• chore: deprecate "dot-syntax"
  • add warnings
  • add a codemod

After release

• docs: update CodeSandbox templates

[vinodhrajamuralidharan]

@layershifter what is the status user.React.forwardRef PR status? I see it is still in open

[layershifter]

@vinodhrajamuralidharan I had a conversation with @levithomason about that PR. The agreement was that he will review it and then we can proceed. I am also waiting for that PR to be merged 😉

[sunech]

Is there any ETA on v3 progress @levithomason / @layershifter ?
There was such a great traction in December, so I started to get my hopes up for SUIR again 🤞 Would hate to see it stall again, with all the great work that has been put in to it 🙏

[layershifter]

3.0.0-beta.0 is out 🎉 Please try and report issues 🙏

[DreierF]

Thanks a lot @layershifter for the effort!
I didn't run into any issues yet with the beta besides the probably expected Typescript issues such as https://stackblitz.com/edit/react-ts-ejdyij?file=App.tsx.

[sunech]

Is there anything further that we can help test, in order to proceed with the v3 release?

[tourman]

@layershifter could you please update the status? FYI @levithomason

1. Is the roadmap todo list still relevant? If not, please refresh or update it. In particular, please add the links to the appropriate PRs, branches, etc.
2. Please add more clear description for each point. E.g. what is Document breaking changes that is not checked?
3. If you are not about to move on with the project, please initiate a process to pass it to the community. There are projects and people who are waiting for the new version trying to replace SUIR with a fork or something else.

[layershifter]

@tourman

1/2. Yes, it's relevant. I will update it to be more precise and detailed 👍
3. To be clear, I don't have time and motivation to maintain this project currently. If there people who are interested in move forward it would be great to hear back 🐱

[sunech]

@layershifter thank you for all you great work so far, highly appreciate your effort!

This project is too good to just die, so I really hope someone wants to pick up from here.
Would love to support if I can, not experienced enough to contribute with code though.
If any freelancers are considering, I would gladly pay for some of your time to get the ball rolling on this again.

[layershifter]

Thanks a lot @layershifter for the effort! I didn't run into any issues yet with the beta besides the probably expected Typescript issues such as https://stackblitz.com/edit/react-ts-ejdyij?file=App.tsx.

@DreierF it's indeed a bug, see #4432 for details.

Is there anything further that we can help test, in order to proceed with the v3 release?

@sunech @tourman I updated changelog and created migration guide (https://react.semantic-ui.com/migration-guide). I also updated issues that needs to be solved to release the next beta. Both issues contain action items and examples of changes needed to be done.

Help on these issues is much appreciated 🐱

[siarheipashkevich]

@layershifter thanks for your work on this package, do you have approximate time when you plan to release 3.0 version?

[layershifter]

3.0.0-beta.2 is out 🎉

It fixes .defaultProps warnings, TypeScript typings & issues with appDir in Next.js.

Please try and report issues 🙏

[fniessink]

I can report that after making a few small changes all frontend unit tests of Quality-time pass with 3.0.0-beta.2:

Test Suites: 85 passed, 85 total
Tests:       694 passed, 694 total
Snapshots:   0 total
Time:        67.751 s, estimated 70 s

Most changes were needed because popups would not appear at the right position with 3.0.0-beta.2. Adding a span or div around triggers solved this. I can't reproduce this issue on the Semantic UI React documentation site so I guess it's an issue on our side.

[dominikdosoudil]

I don't think that it's worth creating a issue but the Sticky component didn't work after the upgrade. I needed to add scrollContext because there is a scrollable div instead of whole window. I am not sure if it's somehow breaking change or I had it wrong even before. I am just mentioning as a possible information to migration guide.

[Noahkoole]

I can report that after making a few small changes all frontend unit tests of Quality-time pass with 3.0.0-beta.2:

Test Suites: 85 passed, 85 total
Tests:       694 passed, 694 total
Snapshots:   0 total
Time:        67.751 s, estimated 70 s

Most changes were needed because popups would not appear at the right position with 3.0.0-beta.2. Adding a span or div around triggers solved this. I can't reproduce this issue on the Semantic UI React documentation site so I guess it's an issue on our side.

This seems to also be an issue on our side. Started with the transition to beta.2 and adding a span around it indeed fixed it

[atti187]

@layershifter - I fixed the first task in the beta-3 release. Could you please add issues for the rest of tasks in the list and I'll see if I can have a go at some of them? Would be nice to get v3 out!

[BlenesiAron]

When is the v3 release scheduled for?

[triemstr]

When is the v3 release scheduled for?

Outside of the eventStack breaking change, it looks like it is just a lot of testing and documentation for the 3.0.0 beta 3 release. I'm not sure if @layershifter is taking pull requests, but maybe some in the community can assist.

[layershifter]

I'm not sure if @layershifter is taking pull requests, but maybe some in the community can assist.

Yep, if somebody is brave enough to get rid of EventStack, I would be happy to review the changes.

[triemstr]

@layershifter Would you consider just going with the current state as version 3 and then working on the rest as version 4?

Only reason is that so many people are getting the props and other javascript warnings now and they don't know that the version 3 beta solves them. Running outdated on npm sources wouldn't show the version 3 beta. Might be a good way to keep the upgrades occurring so that a few more community members may jump in on EventStack.

Just a thought, unless someone is about there on EventStack.

[dominikdosoudil]

@triemstr I am up to looking into the EventStack however there might be one more thing blocking the release that needs to be fixed: https://github.com/Semantic-Org/Semantic-UI-React/pull/4233/files#r1837715017

[dominikdosoudil]

@layershifter So few past days, I've been looking into the EventStack in the Modal (and source code of the event-stack) and there is the thing "eventPool". As I think that I understand that it might help keeping multiple references to same callback (I imagine some independent unsubscribing), I can't really see the real purpose of it (or what and if something would break after removing it).

Could you possibly give me some hint or direction or use case where it's necessary?