-
Notifications
You must be signed in to change notification settings - Fork 18
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
$spec does not work #61
Labels
Comments
Current output is
|
I think the $spec keyword definition has changed in protocol v1.8.x to be supported only at the service root level and reveal the specification of the entire service. This issue should be closed, and open a new issue |
good idea.. lets close and open a new one
…On Mon, Feb 19, 2018 at 12:12 PM, Denny Trebbin ***@***.***> wrote:
I think the $spec keyword definition has changed in protocol v1.8.x to be
supported only at the service level and reveal the specification of the
entire service.
This issue should be closed, and open a new issue $spec always return 404
instead.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADiF7Tcg6WJXcP2hfk1Lbtas83Mvt33kks5tWVcrgaJpZM4PdWw9>
.
--
- Dr. Patrick Bartsch
(web)
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using the $spec keyword on element level, the following error is shown:
GET http://localhost:3000/medialibrary/tracks/$spec
The text was updated successfully, but these errors were encountered: