-
Notifications
You must be signed in to change notification settings - Fork 35
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
Parameter type validation for JSDuck should allow '/' as well as '|' as a value seperator #135
Comments
Thanks, nice catch!
Need to make some option for types parsing algorithm to use '/' instead of '|'. What you think if we just replace |
We use '|' not '/' (I only noticed it when looking for other issues ;-)), so I'd love not only understanding both (which to looks like jsdoctypeparser/jsdoctypeparser#21 fixes) but having the style enforce one or the other for consistency, yeah – but should that be a follow-up (wishlist) issue? |
@jdforrester Yeah, thanks for clarifying that. For now it looks like complicated task cuz we also need some info about used delimiter to check it. Don't see how to check it easily with regexps or something else. Anyway, it's a good idea ;-) |
Per the JSDuck documentation, values can be separated by either '
|
' or '/
'. However, only the first of these works.The text was updated successfully, but these errors were encountered: