-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Exclude special index signature rule from strict subtype relation #53388
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
@typescript-bot test this |
Heya @ahejlsberg, I've started to run the diff-based top-repos suite on this PR at ae63c73. You can monitor the build here. Update: The results are in! |
Heya @ahejlsberg, I've started to run the abridged perf test suite on this PR at ae63c73. You can monitor the build here. Update: The results are in! |
Heya @ahejlsberg, I've started to run the extended test suite on this PR at ae63c73. You can monitor the build here. |
Heya @ahejlsberg, I've started to run the parallelized Definitely Typed test suite on this PR at ae63c73. You can monitor the build here. Update: The results are in! |
Heya @ahejlsberg, I've started to run the diff-based user code test suite on this PR at ae63c73. You can monitor the build here. Update: The results are in! |
@ahejlsberg Here are the results of running the user test suite comparing Everything looks good! |
Hey @ahejlsberg, the results of running the DT tests are ready. |
@ahejlsberg Here they are:Comparison Report - main..53388
System
Hosts
Scenarios
Developer Information: |
Tests and performance are unchanged, except for a new error in |
@typescript-bot pack this |
Heya @DanielRosenwasser, I've started to run the tarball bundle task on this PR at ae63c73. You can monitor the build here. |
Hey @DanielRosenwasser, I've packed this into an installable tgz. You can install it for testing by referencing it in your
and then running There is also a playground for this build and an npm module you can use via |
@ahejlsberg sounds like what you're saying is that TypeORM is supposed to still handle the 0-length case, and can do so by Would you be able to add an equivalentish test case to document this? function foo(obj: Record<string, any> | Record<string, any>[]) {
if (Array.isArray(obj) && obj.length) {
for (let key in obj) {
if (obj[key] !== undefined) {
console.log(obj[key])
}
}
}
else {
for (let key in obj) {
if (obj[key] !== undefined) {
console.log(obj[key])
}
}
}
}
function bar(obj: Record<string, any> | Record<string, any>[]) {
if (Array.isArray(obj)) {
for (let key in obj) {
if (obj[key] !== undefined) {
console.log(obj[key])
}
}
}
else {
for (let key in obj) {
if (obj[key] !== undefined) {
console.log(obj[key])
}
}
}
} |
Confirmed in the test playground that |
I've added the tests, I'm running a task to update the baselines. |
the heck? |
7f4fd9c
to
37911f8
Compare
@typescript-bot cherry-pick this to release-5.0 |
Heya @DanielRosenwasser, I've started to run the task to cherry-pick this into |
Hey @DanielRosenwasser, I've opened #53445 for you. |
…e-5.0 (#53445) Co-authored-by: Daniel Rosenwasser <[email protected]>
…to release-5.0 (microsoft#53445) Co-authored-by: Daniel Rosenwasser <[email protected]>
Fixes #53379.