-
Notifications
You must be signed in to change notification settings - Fork 650
update midnight to React 19 #7523
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
update midnight to React 19 #7523
Conversation
|
i see this is a draft. is it good to put on |
|
should be good to do so - there were a lot of lint issues that I'm going to fix, I just wanted to get the bones up off my PC for looking at |
|
note before i forget: i believe |
e29fc0b to
9fdcf42
Compare
# Conflicts: # scripts/lint-baseline/baseline.ts # src/analysis/retail/mage/fire/guide/SunKingsBlessing.tsx # src/analysis/retail/mage/frost/core/IcyVeins.tsx # src/analysis/retail/mage/frost/talents/Cryopathy.tsx # src/analysis/retail/mage/frost/talents/FrozenOrb.tsx # src/analysis/retail/mage/frost/talents/GlacialSpike.tsx # src/analysis/retail/mage/frost/talents/ShiftingPowerFrost.tsx # src/analysis/retail/monk/mistweaver/modules/spells/ChiBurst.tsx # src/interface/guide/index.tsx
these are primarily noise from the midnight changes to the header, along with changes to an error with dom nesting that we were ignoring before. i've fixed the remaining 2 issues with `validateDOMNesting`, and removed the ignore for the moment, I also enabled `handleExpansionChecker` so that previous-expansion logs in configs pass e2e. this will get turned back off closer to midnight release
Description
Testing
/report/...