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
0.29.1 Upgrade Guide #3415
Comments
This says no breaking changes, but upgrading from 0.29.0 to 0.29.1, I'm getting type errors in my project related to update: looks like it was indeed a small difference in types? Had to change an instance of propEq(value, 'field') to propEq<string | null, string>(value, 'field'). |
ty for the update. This is a good point though, it would be good to coordinate more carefully with the types when cutting releases going forward |
This is great! Thank you, @kedashoe ! |
i am also getting 28 types errors
|
I'm getting the same 28 type errors in node_modules when updating from @types/ramda from 0.29.5 to 0.29.6. |
I can confirm - getting reports of failed builds as well: swagger-api/swagger-js#3176 (because of using ramda as transitive dep). |
@akshayjai1, @klepek42 created a new discussion for the invalid typings at DefinitelyTyped/DefinitelyTyped#67032 |
@Harris-Miller any thoughts on this? I do not believe there were any related code changes, so I would guess people are seeing these issues simply because a new version of ramda resulted in people also getting the newest version of the types which had changes they were not expecting? |
RE: type errors Although we have brought maintaining the type definitions in-house with the ramda/types repo, they still are served through It is something that I'll get on ASAP. To address the main error brought up around Just update to "overrides": {
"types-ramda": "0.29.4"
} This issue was brought up last week at |
Changes from
|
MR for modifyPath update: ramda/types#68 |
[skip ci] The goal of this PR is to have an example app inside the project to improve developer experience and exercise reactotron's capabilities. Currently, you need to have an application configured for Reactotron outside of the project to test. If you want to test the client libraries, you'd have to setup copying those dependencies into your application as an additional step. By adding an example application into the monorepo, we get the following benefits: - Faster feedback loop on client library development - All inclusive reactotron development experience (No external application required; though still supported.) - An application for people to reproduce bugs in shortening time to resolution. - Show examples of usage and conifguration In this PR, I've additionally done the following in support of this effort: - Upgraded Ramda to 0.28.0. I could not go to latest as we are still using Typescript 4.9.5. (ramda/ramda#3415 (comment)) - Upgraded mobx and mobx-state-tree so that our dev dependencies are using the latest versions. - Updated the documentation --------- Co-authored-by: Mark Rickert <mjar81@gmail.com>
v0.29.0...v0.29.1
π₯ Breaking Changes:
None
π Added:
None
π‘ Changes:
β Miscellaneous
π Documentation fixes: #3368 #3373 #3391 #3398 #3402
Many thanks to all the contributors supporting this release.
We'd also like to call out to all those who submitted issues or PRs that we've chosen not to include. It's often easy to forget that the attempts that fail are often just as important to long-term success as those that succeed. Thank you for all your great work! π
The text was updated successfully, but these errors were encountered: