-
Notifications
You must be signed in to change notification settings - Fork 54
Explode modifier not supported? #553
Comments
The URI Template support is a bit lacking at the moment. I'd like to schedule looking into URI Template support near-term. There are various related problems, linking in #500, #456, apiaryio/api-blueprint#252 and apiaryio/snowcrash#357. Right now we're focussed on getting Drafter 4 changes finished and rolled out across Apiary and I think this can be fixed shortly afterwards once we got 4.0 out. |
I know it's open source and whatnot but I'm gonna try asking for a schedule either way 😉 . |
Weeks I hope, #552 should be on of the last PRs (pending any problems we discover during testing). Once that's ready and merged we can being rolling out which will be a delicate and slow process as there are some significant changes to the parse result and we need to be careful rolling out to Apiary and be sure we are not introducing regressions or performance problems. |
As of Drafter 5.0.0-rc.1, full support for URI Template has been added, including level 3/4 and the explode modifier. The included document will now parse without warnings, and show something along the lines of the following in ApiaryUI: |
I'm trying to use the explode modifier with drafter: https://tools.ietf.org/html/rfc6570#section-2.4.2
but I can't get it to work. The API Blueprint spec mentions that RFC6570 is supported though.
Error message:
Code:
The text was updated successfully, but these errors were encountered: