Skip to content

Move OptionDescription to utils/options so types agree #612

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

Merged
merged 5 commits into from
Jun 4, 2019

Conversation

willemneal
Copy link
Contributor

I found this when using the options parser in as-pect and asc.exports disagreed with util.parse's expected argument type Config.

@dcodeIO
Copy link
Member

dcodeIO commented May 28, 2019

Looks good, with my minor comment resolved :)

@@ -3,7 +3,7 @@ export interface OptionDescription {
/** Textual description. */
description?: string | string[],
/** Data type. One of (b)oolean [default], (i)nteger, (f)loat or (s)tring. Uppercase means multiple values. */
type?: "b" | "i" | "f" | "s", "I", "F", "S",
type?: "b" | "i" | "f" | "s" | "I" | "F" | "S",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice find! did that even work before?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nut sure it was ever used. Since it was just the type definition file and no one tried to use the type with a typescript project.

@dcodeIO dcodeIO merged commit 3ed76a9 into AssemblyScript:master Jun 4, 2019
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

Successfully merging this pull request may close these issues.

2 participants