[TypeScript] Props type infer about composition-api HOT 14 CLOSED

1. If you don't need typescript types

export default createComponent({
  setup(props) {
    return {}
  },
  props: {
    simple: {
      type: String,
      required: true
    },
  } as const
})

interface Props {
  simple: string
}

2. If you need typescript types

export default createComponent({
  setup(props) {
    return {}
  },
  props: ({
    advanced: {
      required: true
    },
  } as unknown) as Props
})

interface Props {
  advanced: {
    a: string
    b: number
  }
}

from composition-api.

THX very much

from composition-api.

I still got error:

Conversion of type '{ readonly list: ArrayConstructor; }' to type 'Props' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
  Types of property 'list' are incompatible.
    Type 'ArrayConstructor' is missing the following properties from type 'GridMenuList[]': pop, push, concat, join, and 27 more.Vetur(2352)
Conversion of type '{ readonly list: ArrayConstructor; }' to type 'Props' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
  Types of property 'list' are incompatible.
    Type 'ArrayConstructor' is not comparable to type 'GridMenuList[]'.

when

interface Props {
  list: GridMenuList[]
}

const DropdownGrid = createComponent({
  props: ({
    list: Array
  } as const) as Props,
  setup(props) {
  ...

So maybe I still need to convert to unknown first?

from composition-api.

There was an error in my example, I've fixed it.

from composition-api.

I got error when

• as unknown as Props as const
• as unknown as const as Props

and no const effect when as const as unknown as Props

So how should I do?

from composition-api.

Oh thx, so when I want types I can not convert to const, is that right?

from composition-api.

By the way, I don't think we need that parentheses(I am not sure whether I spell right). It seems ok when I remove it.

from composition-api.

I don't use as const with interface Props If you want to be sure to not assign to props I think you can do as unknown as Readonly<Props>

from composition-api.

My linter adds parenthesis but It's not required

from composition-api.

@GODOFHOPE Try v2.2.0.

from composition-api.

🆗，I'll try ^-^

from composition-api.

Excuse me ,waht's impoving? I cannot feel any enhancement. Could you tell me more specificitly?
I stitll catch error whtn writing originally, yet I still needs to convert to unknown.

from composition-api.

I noticed the provide/inject types improve, by checking your commits and I alse noticed an enhancement with states, but none about props.

from composition-api.

@GODOFHOPE Can you show me your codes? An online example would be great.

from composition-api.