Skip to content

Feature Request: More aggressive types #204

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

Open
mcnuttandrew opened this issue Feb 6, 2020 · 0 comments
Open

Feature Request: More aggressive types #204

mcnuttandrew opened this issue Feb 6, 2020 · 0 comments

Comments

@mcnuttandrew
Copy link

mcnuttandrew commented Feb 6, 2020

Thanks for the wonderful library! I think it would be really great if the types documented the API of the component a little more closely. For instance the type of "placement" is string, whereas the actual allowed values (according to the readme) are 'left','right','top','bottom', 'topLeft', 'topRight', 'bottomLeft', 'bottomRight'. It would be great if the type knew about all of the things that the documentation knew about, which allows autocompleters/intellisensers to be able to provide in context documentation.

(I'd be happy to help if you are busy with other things!)

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

1 participant