You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would rather take the existing codebase, transfer it to swift and go from there. I only use this parser because of the abstinence of a Swift version.
I would love to help out on that though.
I was just making false assumptions. I thought generating the parser would generate all the files and features, while in fact the generated part is really just the one main handler. This got me confused because there is a new version for it(The gherkin and objc grammar files) but the codebase was outdated.
I can surely work on a swift version of that.
I do have some experience with objective c but not nearly as much as with Swift, that's why I'd prefer to transfer it over to Swift. Plus the fact that Swift is now Apple's main language.
It's only the parser that is generated from the grammar. The lexer/scanner and AST builder logic is hand-written.
I realise it might be a bit daunting to become familiar with the ObjC codebase and the build system, but we're here to help. We usually hang out in Slack and we also have weekly committer meetings on Zoom every Thursday at 3pm BST - see the #committers channel for more details.
The rule keyword is now part of the grammar file, but the Parser fules are still outdated and lack support for it.
The text was updated successfully, but these errors were encountered: