Ladislav Prskavec

Results 56 issues of Ladislav Prskavec

@Almad opened apiaryio/snowcrash#334 Warnings are confusing if method name is not written all-CAPS and therefore not recognised. Snowcrash should recognise the line (be case-insensitive) and issue a warning. Fore more...

improvement

@klokane opened apiaryio/snowcrash#355 As say Blueprint specification: https://github.com/apiaryio/api-blueprint/blob/master/API%20Blueprint%20Specification.md#def-uriparameters-section ``` Members is the optional enumeration of possible values. should be surrounded by enum[] if this is present. For example, if enumeration...

improvement

@jonatron opened apiaryio/snowcrash#370 I had a non breaking space (0xA0) in my apib file after a # in a heading, and it was very hard to find out that it...

question

@kylef opened apiaryio/snowcrash#378 Given the following example: ``` apib ## Data Structures ### datetime (string) An ISO8601 formatted date. #### Sample 2015-10-15T13:21:09Z ``` Where we have a sample value of...

bug

@goganchic opened apiaryio/snowcrash#438 Recently I've found such test https://github.com/apiaryio/snowcrash/blob/master/test/test-ResourceGroupParser.cc#L103-L133 It tries to process such apib with resource group parser: ```apib # Group ## /r1 p1 ## /r2 p2 ``` This...

@zdne opened apiaryio/snowcrash#29

bug
improvement

@zdne opened apiaryio/snowcrash#31 Following blueprint is parsed as with API Name `POST` and the rest of keywords as a API description. Parser should warn about this. `````` FORMAT: X-1A ##...

improvement

@zdne opened apiaryio/snowcrash#41 Currently only [some characters](https://github.com/apiaryio/api-blueprint/blob/master/API%20Blueprint%20Specification.md#36-identifiers) are allowed in API Blueprint [identifiers](https://github.com/apiaryio/api-blueprint/blob/master/API%20Blueprint%20Specification.md#36-identifiers). If illegal character is used the whole section is silently ignored. Following blueprint should at least produce...

improvement

@zdne opened apiaryio/snowcrash#42 HTML entities such as `—` should be escaped in non-description nodes (e.g. name). In description nodes of AST it should be controlled by the rendering parser flag....

improvement

@zdne opened apiaryio/snowcrash#51 Usually parser warnings are treated very seriously; maybe differ between business error and HTTP spec violation

improvement