ldthomas / apg-js2 Goto Github PK

I was just having a quick play around with APG, and I'm getting errors for case-sensitive literal text strings introduced in RFC 7405 (which updates RFC 5234). For example:

keyword = %s"array" / %s"bool"

Results in Unrecognized SABNF element. for both instances of %s.

In addition, RFC 5234 is case insensitive, and the parsers that APG currently generates do not seem to be honoring this (I say this from looking at the generated parser, and only seeing ASCII values for exact case matches):

ABNF strings are case insensitive and the character set for these strings is US-ASCII.

Hence:

rulename = "abc"

and:

rulename = "aBc"

will match "abc", "Abc", "aBc", "abC", "ABc", "aBC", "AbC", and "ABC".

Most of the functionality could be exported to apg-js2-lib in order to make the apg-js2 suite of packages platform agnostic and would enable packages like apg-js2-exp compatible with react native (ldthomas/apg-js2-exp#3)

An alternative would be to make a apg-js2-parse lib or something...

What do you think?

Hi Lowell,

Having downloaded http://docs.oasis-open.org/odata/odata/v4.01/cs01/abnf/odata-abnf-construction-rules.txt and launched

apg -i odata-abnf-construction-rules.txt

some tens of minutes ago, I still watch my CPU at 100% with zero bytes output.

Is there a way to obtain some sort of real time debug print just to guess if it worth waiting? The -v command line switch gives the version number and I didn't find any key to verbose mode.

Thank you in advance.

I seem to be getting that ALPHA and WSP, etc. aren't defined. This are specified in the core rules section of the rfc spec. Am I missing where these are or are they not implemented in this parser? Thank you!

I'm trying to use this library in the browser in a webpack application instead of a browserify application. Everytime it tries to build the bundle it complains about not being able to resolve the 'fs' module. Would you have any advice on solving this? I'll post any updates here for future users if I have any luck.