apiaryio / apiblueprintorg Goto Github PK

Idea: https://apiblueprint.org/tools.html page could have a button "Add your tool", which would lead to GitHub editor, similar to "I want to be on the list" button here.

Following link from https://apiary.io/blueprint to tooling section of apiblueprint.org site I got 404, quick look to gh-pages branch shows that index.html is in place. Trying http://apiblueprint.org it goes to https version and returns 404, isn't the https the problem AFAIK gh-pages are http only?
Or is it just me and everything works just fine and error is between the chair and keyboard?

Copy & pasted a blueprint in safari to editor at apiblueprint.org – the parser refuses to parse the blueprint complaining that it is not UTF-8 (it was lowercase utf-8):

Note quite annoyingly a modal alert dialoged popped up first an only after that the same message has appeared in the AST area.

It would be good to get rid of the alert popup as well.

If a blueprint starts with metadata (as most of blueprints from documentation, tutorials and apiary do) the /parse endpoint fails to parse them properly

cURL example

Call

curl --include -X POST https://apiblueprintapi.apiary-proxy.com/parser --header "Content-Type:text/vnd.apiblueprint+markdown; version=1A" --header "Accept:application/vnd.apiblueprint.parseresult.raw+json" -d 'Format: 1A\n\n # API Name\n'

Actual Output

{
  "ast": {
    "_version": "2.0",
    "metadata": [
      {
        "name": "Format",
        "value": "1A\\n\\n # API Name\\n"
      }
    ],
    "name": "",
    "description": "",
    "resourceGroups": []
  },
  "warnings": [],
  "error": null,
  "_version": "1.0"
}

Correct Output

{
  "ast": {
    "_version": "2.0",
    "metadata": [
      {
        "name": "FORMAT",
        "value": "1A"
      }
    ],
    "name": "API Name",
    "description": "",
    "resourceGroups": []
  },
  "warnings": [],
  "error": null,
  "_version": "1.0"
}

https://apiblueprint.org/documentation/

The left menu is strange - the MSON link has the same url as "second” Tutorial, there are two tutorials, etc. Also the “active” state doesn’t persist on the menu item, so I don’t know where I am currently.

Entering an invalid blueprint on apiblueprint.org results in annoying modal pop-up with the JSON instead of a warning message in the gutter of the blueprint edit area as before.

This is a regression issue and it dramatically affects the usability of the interactive editor at apiblueprint.org

Please revert the behavior to its original state.

Favicon is missing (old one is cached) - by @freaz

...so TravisCI doesn't fail on this branch and, primarily, all branches built on top of gh-pages.

by @abtris

The output in the "AST" window should suffice...

All the example pages linked from the docify readme 404, which has been an issue since December 2014.