Skip to content
This repository has been archived by the owner on Nov 8, 2024. It is now read-only.

Member Type Separator incorrectly breaks parsing #127

Closed
zdne opened this issue Sep 28, 2015 · 0 comments
Closed

Member Type Separator incorrectly breaks parsing #127

zdne opened this issue Sep 28, 2015 · 0 comments
Labels

Comments

@zdne
Copy link
Contributor

zdne commented Sep 28, 2015

Following blueprint

# Resource [/r]

## POST

+ Properties

+ Request
    + Body

            {} 

+ Response 201

results in (incorrect)

warning: (6)  action is missing a response :17:9
warning: (5)  ignoring unrecognized block :26:14
warning: (5)  ignoring unrecognized block :40:39
warning: (5)  ignoring unrecognized block :79:15

The - properties chokes parser – apparently due to being recognized as member type separator but on an unexpected point.

The correct behavior should be to parse it as POST action description and (optionally) report it as a possible keyword.

@zdne zdne added the bug label Sep 28, 2015
kylef added a commit that referenced this issue Jul 13, 2016
* Fixes member type separator causing unrecognized block warning

Fixes #127
@kylef kylef mentioned this issue Jul 13, 2016
@w-vi w-vi closed this as completed in #361 Jul 14, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant