-
Notifications
You must be signed in to change notification settings - Fork 54
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
New style parameter breaking when using backtick #123
Comments
To follow up from the above, if I run the command:
with a warning:
The "name" should be "order_by" without the ": transaction_date". If I remove all the underscores it works as expected. |
|
When trying it with the following changes:
I get the following warning:
|
Can you please give us the complete blueprint? |
I'm testing the underscores, and using this blueprint:
which results in an output with warnings here: My command: |
Hi, just wondering if you could replicate that above using that blueprint I provided? |
@earnaway Looks like this is a bug on our side. The ``` are affecting the new style parameter recognition somehow. |
Any idea if this is on the radar to update and fix fairly soon? Or just a rough ETA on it if you have an idea? Thanks. |
Hi @pksunkara - just wondering if there was any recent update to this with the ``` issue? Thanks! |
Hi @earnaway, we don't have any updates yet. But this is on our radar, we have some a couple of regression issues which we need to tackle first before getting to this one. We'll be sure to update this issue when we get to working on this. |
Thanks @kylef |
Any time estimate on this? |
@Clar64 Unfortunately, we are currently working very hard on getting MSON and Attributes out. Once that is done, this bug is very high on our priority list and we would love to fix this as soon as possible. |
Thanks, we appreciate it! On Fri, 20 Nov 2015 16:38 Pavan Kumar Sunkara notifications@github.com
|
Any update on this? This issue is too annoying to make other guys in the team believing in api-blueprint... |
ditto |
This has now been fixed in parser master branch. We will be incorporating it in Apiary soon. |
Awesome. Thank you!! |
Excellent! Thank you 👍 |
Any update? |
Unfortunately, this is not yet deployed. We will update you as soon as it is. |
This bug was resolved in Drafter 2.3.0-pre.0, and it has been rolled out to Apiary providing you are behind the Attributes Kit feature flag. |
What would be the best/easiest way to install |
@earnaway You can use homebrew to install the latest drafter 3.2.x. The command is follows:
|
Guys we can do this: + Parameters
+ `grant_type`: `refresh_token` (string, required) - Tipo de concessão Works great! |
I originally posted this in the aglio repo, but apparently it's caused by the drafter code, not the aglio, so thought I'd ask in here if drafter was where the bug was. Thanks.
I've noticed an issue when there are underscores as part of the params in the resources.
Here's an example:
When running aglio against the above with the following command
"./node_modules/aglio/bin/aglio.js --theme-style default -i test.apib -o test.html"
then I get the following warning:
And the generated html looks like:
I've noticed if I remove all the underscores in the examples, it works as expected, so must be an issue with the way it handles underscores in the parameters.
My aglio version is:
aglio 2.0.4
olio 1.2.1
The text was updated successfully, but these errors were encountered: