You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
interfaceEntryBase{/** * Type info... */type?: 'default'|'declaration'/** * Output base info... */output?: string/** * Format base info... */format?: string/** * Name base info... */name?: string}interfacePluginsDefault{/** * Esbuild plugin info... * * @default undefined */esbuild?: Record<string,unknown>}interfaceEntryDefaultextendsEntryBase{/** * Input default info... */input: string/** * Name default info... */name?: string/** * Plugins default info... * * @default undefined */plugins?: PluginsDefault}interfacePluginsDeclaration{/** * Dts plugin info... * * @default undefined */dts?: Record<string,unknown>}interfaceEntryDeclarationextendsEntryBase{/** * Declaration info... */declaration: string/** * Plugins declaration info... * * @default undefined */plugins?: PluginsDeclaration}typeEntriesOptions=EntryDefault|EntryDeclarationconstoptions: EntriesOptions[]=[/** * Honestly here I would expect TypeScript to be smart enough * to automatically inffer types based on only one required property (`input`) * and picks correct interfaces and all descriptions but I can assume * that this is more complex than it sound */{input: './src/index.ts',output: './dist/index.mjs',// no description or autocomplete plugins: {esbuild: {}},// no description or autocomplete name: 'default name',type: 'default'},/** * Also again only one required property `declaration' so it would be nice if * TypeScript could automatically infer the whole interface correctly */{declaration: './src/types.ts',output: './dist/types/index.d.ts',format: 'esm',// no description or autocomplete plugins: {dts: {}},// no description or autocomplete name: 'declaration name',type: 'declaration'}]/** * I searched a lot on the net and came across this example https://stackoverflow.com/questions/73155261/how-to-narrow-down-a-generic-type-based-on-object-property-type * where `jcalz`describes and gives an example how to narrow the types based on object keys, * but I guess this is the current working solution and doesn't work in all cases, * I also wonder how to do it when the key property is optional and not specified in object? */typeExtractOnProp<T,KextendskeyofT,V>=Textendsunknown ? VextendsT[K] ?
{[PinkeyofT]: PextendsK ? T[P]&V : T[P]}
: never : nevertypeEntriesOptionsPerProp=ExtractOnProp<EntryDefault,'type','default'>|ExtractOnProp<EntryDeclaration,'type','declaration'>functiondefineConfig(options: EntriesOptionsPerProp[]): EntriesOptionsPerProp[]{returnoptions}defineConfig([{input: './src/index.ts',output: './dist/index.mjs',plugins: {esbuild: {}},name: 'default name',type: 'default'},{declaration: './src/types.ts',output: './dist/types/index.d.ts',format: 'esm',plugins: {dts: {}},name: 'declaration name',type: 'declaration'},// does not work if `type` is not defined{input: './src/index.ts',output: './dist/index.mjs',plugins: {esbuild: {}},name: 'default name',},])
π Actual behavior
Hi, as discussed in previous issue #56082 and the merged PR, it seems like this area could use some internal improvements.
When we have multiple interfaces that extend the base interface, then the types are not picked up correctly when defining a new array of object unions.
Also, properties from the object do not get description information or offer correct auto-completion which can be confusing.
π Expected behavior
I expect it to offer the correct auto-completion for each object and give the right information when I hover over a property to see the type or description of what that option does.
Additional information about the issue
I mentioned some examples and expectations of behavior in the playground.
The text was updated successfully, but these errors were encountered:
I intentionally left comments and separate interfaces (because they extends the base one), so that one can see which description is displayed and which is not in the quickinfo after hovering over the property inside object.
The example is actually very simple which can be seen in the playground.
// code from playgroundinterfaceEntryBase{/** * base */type: 'default'|'declaration'output?: stringformat?: stringname?: string}interfacePluginsDefault{esbuild?: Record<string,unknown>}interfacePluginsDeclaration{dts?: Record<string,unknown>}interfaceEntryDefaultextendsEntryBase{/** * default */input: string/** * default */name?: string/** * default */plugins?: PluginsDefault}interfaceEntryDeclarationextendsEntryBase{/** * declaration */input: string/** * declaration */plugins?: PluginsDeclaration}typeEntriesOptions=EntryDefault|EntryDeclarationconstoptions: EntriesOptions[]=[{type: 'default',// =>input: './src/index.ts',// => no quickinfo when hoverplugins: {dts: {}},// => should be an error here, also no quickinfo when hovername: 'default name',// => no quickinfo when hover},{type: 'declaration',input: './src/types/index.ts',// => no quickinfo when hoverplugins: {esbuild: {}},// => should be an error here, also no quickinfo when hover},]
π Search Terms
"array of object unions", "array union narrowing", "union narrowing", "object union operator in"
π Version & Regression Information
5.2.2
and the latest5.6.2
β― Playground Link
Playground
π» Code
π Actual behavior
Hi, as discussed in previous issue #56082 and the merged PR, it seems like this area could use some internal improvements.
When we have multiple interfaces that extend the base interface, then the types are not picked up correctly when defining a new array of object unions.
Also, properties from the object do not get description information or offer correct auto-completion which can be confusing.
π Expected behavior
I expect it to offer the correct auto-completion for each object and give the right information when I hover over a property to see the type or description of what that option does.
Additional information about the issue
I mentioned some examples and expectations of behavior in the playground.
The text was updated successfully, but these errors were encountered: