Skip to content
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

API Blueprint parsing issues? #5

Open
cojoj opened this issue Aug 3, 2015 · 6 comments
Open

API Blueprint parsing issues? #5

cojoj opened this issue Aug 3, 2015 · 6 comments
Labels

Comments

@cojoj
Copy link

cojoj commented Aug 3, 2015

From line 133 there's some sort of syntax parsing issue...
After this:

# Bot [/bots/{id}]

+ Model (application/json)

syntax highlighting on github and also in Sublime Text 3 is broken... Looks like one object is not closed or some brackets are missing.
It's worth taking a look since working without syntax highlight is PITA 😢

@cojoj
Copy link
Author

cojoj commented Aug 3, 2015

There's some problem with parsing

+ Model (application/json)

section.
In line 419 same thing happens that after Model syntax is lost... But if you comment out model JSON everything's back to normal.

@czechboy0
Copy link
Member

Haha this is insane. It seems like the API blueprint parser is confused by the underscores in Bot's key names _id, _rev etc. Try removing the underscore and the highlighting fixes itself.

I'll report it to them.

@czechboy0
Copy link
Member

@cojoj I only see the highlighting broken in Sublime Text and on GitHub, but not at Apiary.io. They must be using a different parser.

@czechboy0
Copy link
Member

@cojoj
Copy link
Author

cojoj commented Aug 4, 2015

Well, well, well... Hope they'll fix it soon 😉

Yeah, Apiary.io works correctly but I have one question. Why

## List all Bots [GET]

+ Response 200

        {
            "count": 2,
            "results": [
                [Bot][],
                [Bot][]
            ]
        }

Isn't displayed correctly on Apiary.io?

@czechboy0
Copy link
Member

Because it's not officially supported 😆 I just did it in the meantime before we switch to MSON at some point.

@czechboy0 czechboy0 added the bug label Aug 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants