Skip to content
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

all types are declared as optional #27

Closed
sedghi opened this issue Mar 2, 2022 · 3 comments
Closed

all types are declared as optional #27

sedghi opened this issue Mar 2, 2022 · 3 comments

Comments

@sedghi
Copy link

sedghi commented Mar 2, 2022

I'm facing a strange behaviour where all the type properties are declared as optional even if they are mandatory. Here is one of my type aliases (it happens for all of them actually)

type Metadata = {
  BitsAllocated: number
  BitsStored: number
  SamplesPerPixel: number
  HighBit: number
  PhotometricInterpretation: string
  PixelRepresentation: number
}

which renders to

image

although I have noticed that option flag does not appear when minimal=false, so it is just the header that is wrong. I noticed it only happens for type aliases not interfaces

@sedghi
Copy link
Author

sedghi commented Mar 3, 2022

I can confirm function arguments are fine, this is only happening for types

@milesj
Copy link
Owner

milesj commented Mar 4, 2022

Fixed in the latest version

@milesj milesj closed this as completed Mar 4, 2022
@sedghi
Copy link
Author

sedghi commented Mar 4, 2022

Amazing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants