-
Notifications
You must be signed in to change notification settings - Fork 1.1k
chore: upgrade to [email protected] #4051
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
Conversation
59a1093
to
7e6e22b
Compare
@raymondfeng , any reasons that we are renaming the |
It's a workaround/fix for microsoft/TypeScript#34761. Considering we have:
TypeScript 3.7.x tries to emit db.datasource.d.ts for both files and complains about the conflict. |
@raymondfeng nice catch on that. I read the whole issue on typescript and now I understand better. LGTM !. I see conflicts of course with current applications in that they will need to manually change the Just a question: Isn't it possible to just move it to its own config directory ie: |
3a69ea2
to
e65ebde
Compare
Can we leave this change out of this pull request please and let RenovateBot do the job? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The git history is not as clean as I would like it to be. Other than that, the patch LGTM.
"rimraf": "^3.0.0", | ||
"source-map-support": "^0.5.16", | ||
"typescript": "~3.6.4", | ||
"typescript": "~3.7.2", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am surprised to see this change as part of the commit chore: refresh package-lock.json
, I would expect it to be a part of chore: upgrade to TypeScript 3.7.2
.
e65ebde
to
4996c5b
Compare
Good day i update typescript only for test error first error is
Second error later of rename from reactions.datasource.ts to reactions.datasource.d.ts
how can solve this? |
@jomarocas, the naming convention for the datasource has been changed. Your problem should be fixed by renaming the datasource json files For details, please see #4173 (comment). |
Blocked by typescript-eslint/typescript-eslint#815(fixed by b21c2ce)Worked around microsoft/TypeScript#34761
Checklist
👉 Read and sign the CLA (Contributor License Agreement) 👈
npm test
passes on your machinepackages/cli
were updatedexamples/*
were updated👉 Check out how to submit a PR 👈