Comments (12)
See https://github.com/microsoft/TypeScript/wiki/FAQ#indirect-excess-properties-are-ok
from typescript.
Indirect excess properties are not an error. Examples of indirect excess properties would be:
- values returned by functions
- values stored in intermediate variables
b
is direct. You go straight from value→property.
c
in indirect because it is one step removed. You have a getter, which is a function that returns a value.
From the linked FAQ, excess property checks are to defend against things like typos:
const p: Dimensions = {
width: 32,
height: 14,
depht: 11 // <-- typo!!
}
But there are plenty of situations where you want or need to allow extra properties.
from typescript.
You are conflating two different things. The autocomplete thing is unrelated to the type checking of c.data
.
b.data
andc.data
should throw errors simultaneously or not
No, they shouldn't; it's already been explained several times why c.data
doesn't have an error. The excess property check doesn't apply to it, but it's still type-checked properly. For example if you change the code to
const c: T = {
get data() {
return 42;
},
};
then you get a type error.
from typescript.
You are conflating two different things. The autocomplete thing is unrelated to the type checking of
c.data
.
b.data
andc.data
should throw errors simultaneously or notNo, they shouldn't; it's already been explained several times why
c.data
doesn't have an error. The excess property check doesn't apply to it, but it's still type-checked properly. For example if you change the code toconst c: T = { get data() { return 42; }, };then you get a type error.
Thank you, I understand my mistake
The real problem should be automatic completion
The problem of automatic completion made me think that c.data
had changed to any
type, resulting in the loss of type checking
from typescript.
See https://github.com/microsoft/TypeScript/wiki/FAQ#indirect-excess-properties-are-ok
bug b.data.b
throw type error. and in c.data
no type prompt like any
,
see typescirpt palay
from typescript.
Sigh... I really wish the wording of this error message would be changed.
This isn't a bug. The excess property check error is not a type error, it's a lint check. You can't rely on it to prevent extra properties from being put on an object because it won't always trigger (which is by design). If that's what you need, see #12936.
The other issue you linked to this (#49511) is unrelated - there is nothing like an any
involved here. { a: number, b: number }
is a legal subtype of and assignable to { a: number }
.
from typescript.
When inspecting the code I do find something looks like a bug: #58484.
@lqzhgood , is it what you are talking about?
from typescript.
Sigh... I really wish the wording of this error message would be changed.
This isn't a bug. The excess property check error is not a type error, it's a lint check. You can't rely on it to prevent extra properties from being put on an object because it won't always trigger (which is by design). If that's what you need, see #12936.
The other issue you linked to this (#49511) is unrelated - there is nothing like an
any
involved here.{ a: number, b: number }
is a legal subtype of and assignable to{ a: number }
.
The focus of this issue is not on whether additional attributes can be added,
Is difference types of b.data
and c.data
by use getters
b.data
and c.data
should throw errors simultaneously or not
from typescript.
When inspecting the code I do find something looks like a bug: #58484. @lqzhgood , is it what you are talking about?
yes,
d.data
and c.data
(getter) Inconsistent types returned,(from the perspective of throwing exceptions)
and c.data
looks like any
in autocomplete
from typescript.
Indirect excess properties are not an error. Examples of indirect excess properties would be:
- values returned by functions
- values stored in intermediate variables
b
is direct. You go straight from value→property.
c
in indirect because it is one step removed. You have a getter, which is a function that returns a value.From the linked FAQ, excess property checks are to defend against things like typos:
const p: Dimensions = { width: 32, height: 14, depht: 11 // <-- typo!! }But there are plenty of situations where you want or need to allow extra properties.
Thank you for your answer, but c.data
look like any
in autocomplete.
from typescript.
In that case, this is a retroactive duplicate of #58484 😄
from typescript.
the real problem is #58484. I will close this issue
from typescript.
Related Issues (20)
- Method `concat` has wrong typization HOT 3
- Invalid type inference for optional chaining operator when nullish check is extracted to `const` varaiable HOT 2
- Inline type annotations for destructured properties using angle bracket syntax HOT 3
- Enum generic does not restrict union of possible objects where enum is defined HOT 8
- `const wrong = () => (1 < 3) as true // type: () => true` this should be an error. HOT 9
- "Organize Imports" should adjust specifiers based on preferences HOT 1
- TS 5.4.5: Return type for performance.getEntriesByType is inaccurate
- Lose generic when spreading `T | undefined` where T is a generic object type HOT 3
- [isolatedDeclarations][5.5] Optional parameter annotated with imported type has isolatedDeclarations error HOT 2
- Missing content in documentation FAQ section HOT 3
- Make property decorator fabrics share generics with corresponding methods HOT 2
- Generic type parameter not inferring properly HOT 1
- JSDoc `@private` on constructor without parameters is omitted in declaration files
- [API] Ability to check if a parameter is being passed to const type parameter
- Improve support for internal packages by resolving path aliases
- CommonJS globals permitted for ES module builds with no compiler error. HOT 4
- -
- Type predicate doesn't narrow down function overload (but assertion works) HOT 3
- Recursive type strangely resolved to never HOT 3
- [5.5 beta] The `moduleDetection` option is ignored for `verbatimModuleSyntax` error HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from typescript.