I had a slightly different approach to providing code samples in different languages than your https://github.com/apiaryio/language-templates
You can see it at https://github.com/andreineculau/apiary.syntax.js
Raw apiary syntax is provided to a function which parses it into an apiary object. From there, one can produce any code sample at run-time (when the user switches in the browser), rather than at compile-time (when you render the page).
Just a thought.1 vote
Done with our open-sourced parser.
The current font used for headers (Helvetica) does for some reason not contain many accented variants such as ť, č etc. It would be great if it was replaced with a font better covering foreign characters (Helvetica Neue).1 vote
For example, an API to check if you are following a user, when the result is 'YES', return 204 status code, else return 404 status code.1 vote
We’ve had this functionality for a while, my apologies for having this buried in documentation. Here is all the info you need:
I thought you had a designer on you team!4 votes
Yay, we have that favicon captured. For quite some time now. Thanks for reminding.
To protect user password, login page should be on https page.0 votes
Swagger has convenient way to try API calls from the web page. Maybe Apiary does as well but I wasn't able to figure it out.6 votes
The requested feature “All we want is Try It out…” is now live and deployed.
Go to Documentation > any resource > tab “Try it” (next to Example / Debugger / Comments) and enjoy.
One click simplicity and beauty in an easy step.
Even though still an Internet-Draft http://tools.ietf.org/html/draft-ietf-appsawg-media-type-suffix-regs-00, it's rather wide-spread to consider application/vnd....+json to have the same syntax as application/json. I believe that +xml has a higher level of adoption.
So, when colorizing the payload based on the content-type, would be nice to look also at these suffixed content-types.1 vote
+json now forces proper brush
In inspector, JSON diff is now used regardless of content-type send if payload is parseable JSON.
It's frustrating on a large API to scroll back down to the area you were just editing1 vote
Page is now not reloaded on save.
For variety of reasons, it may make sense to disable comments in documentation.
Add a switch in settings for it.3 votes
Turns out it’s quite easy, so it’s done.
Body diff does not work. It does not parse newline chars correctly.
Currently diff works on text/line-based basis. We will offer JSON/XML tree diffs in the future.
However, this was bug caused by condensing multi-line responses into one and has been fixed.
When hitting an invite link, it'd be great if the invite code itself that showed on the first form was still set on the Github signup form.1 vote
Both twitter and github registration now maintains an invite code.
I'm used to being able to either see a live preview of my markdown code or at least have a way to preview it to make sure i didn't mess anything up before saving.5 votes
Local preview is supported via apiary client.
Client is distributed as ruby gem: you can install it via (sudo) gem install apiary.
Use apiary —help to display usage, README is available in repository: https://github.com/apiaryio/apiary-client#apiaryio
Please feel free to submit bug reports/patches to our github repository.
took some experimentation to get it working1 vote
Thanks for the feedback. We’ve launched a more comprehensive blueprint documentation a couple weeks back at http://apiary.io/blueprint
curl defaults to POST if --data is present1 vote
Thanks for noticing.
Checked FF and Chrome1 vote
Leak fixed, thanks.
Can you make the matching bracket 'flash' whenever you close a bracket, please please pretty please :)1 vote
we’ve just rolled out a massive update to the code editor, including bracket matching, syntax highlighting, support for XML and JSON etc.
- Don't see your idea?