We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm submitting a bug report
Current behavior: In the API docs on http://aurelia.io complex signatures are not displayed.
Expected/desired behavior:
What is the expected behavior? For example on http://aurelia.io/docs/api/fetch-client/interface/Interceptor/property/request the return signature should be Request | Response | Promise<Request | Response> and on http://aurelia.io/docs/api/router/interface/RoutableComponentActivate/method/activate it should be Promise<void> | PromiseLike<void> | IObservable | void.
Request | Response | Promise<Request | Response>
Promise<void> | PromiseLike<void> | IObservable | void
What is the motivation / use case for changing the behavior? Accurate type definitions.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I'm submitting a bug report
Chrome 62 | Firefox 57
Current behavior:
In the API docs on http://aurelia.io complex signatures are not displayed.
Expected/desired behavior:
What is the expected behavior?
For example on http://aurelia.io/docs/api/fetch-client/interface/Interceptor/property/request the return signature should be
Request | Response | Promise<Request | Response>and on http://aurelia.io/docs/api/router/interface/RoutableComponentActivate/method/activate it should bePromise<void> | PromiseLike<void> | IObservable | void.What is the motivation / use case for changing the behavior?
Accurate type definitions.
The text was updated successfully, but these errors were encountered: