-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
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
Tutorials need to show ReactDOM.createRoot()
to match React 18
#4480
Comments
I'm happy to work on this and update the tutorials for React |
@marksist300 unfortunately it's more complicated than just updating a couple of |
Ah, ok. I thought rebasing public repos was generally a 'no no'? |
Usually! But in this case, it's a template/example repo. The main purpose is to have a known sequence of commits that build the example app step-by-step, and the CodeSandboxes in the tutorial pages link to specific commits by tag so they can show the state of the code as of those commits. The other use case is that the first commit in the repo has all the dependencies listed and the basic scaffolding, so that learners can clone the repo and follow along with the tutorial by writing each step themselves. Given that, users don't care about the history of the repo, exactly. There's no ongoing development, no one is going to clone it and try to push feature branches, etc. Also, all the rebasing I'm talking about is solely for the |
OK. Probably best left to someone who knows exactly what should and shouldn't be included from the git history then 🙂. I was looking through the Redux fundamentals last night and noticed the docs are using Wasn't sure it would warrant a separate issue, but it should probably be added to the list of code snippets to update as it's deprecated. It's used on several pages. |
I take that back, the "Fundamentals" tutorial repo still needs to be updated. |
Both the "Essentials" and "Fundamentals" tutorials are currently showing
ReactDOM.render()
, and that needs to be update to match React 18.The text was updated successfully, but these errors were encountered: