-
Notifications
You must be signed in to change notification settings - Fork 62
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
Test case doesn't work anymore #54
Comments
@david542542 Hi! You are right, the expected input format has changed since the latest release, but in the opposite direction as you might think: defining --unlexer and --unparser is the old way, now we are using fully qualified names (like HTMLCustomGenerator.HTMLCustomGenerator in the example). The problem with the failing setup above is that you probably installed the latest release of Grammarinator (e.g., from PyPI with You have two options the fix the issue:
|
@renatahodovan fantastic, thanks so much for the response and such an awesome project! I've gotten it to work based on your above feedback -- I ended up just installing it from Github source, instead of pip. Thanks again! |
It seems perhaps the format was updated to accept two different files, one for lexing and one for parsing. Running the default example I get:
Actually, I wasn't able to get this to work with the separated files (the tree itself would always error). Any feedback or update on how to use this would be great. Thanks
The text was updated successfully, but these errors were encountered: