I've been able to compile the UniFFI bindings into a library for Python. Everything seems to work just fine. However, I've noticed that the parse_recipe function that the bindings export specifically uses the canonical parser:
let parser = cooklang::CooklangParser::canonical();
In my project I'd like to support the extended features. As a step in that direction, I updated my local build process to patch bindings/src/lib.rs to use this line instead:
let parser = cooklang::CooklangParser::extended();
This proved insufficient, however, as other changes appear to be needed. For example, the exported Ingredient class lacks the alias attribute that would be populated by the extended parser.
Could the bindings be updated to make the extended parsing available?
I've been able to compile the UniFFI bindings into a library for Python. Everything seems to work just fine. However, I've noticed that the
parse_recipefunction that the bindings export specifically uses the canonical parser:In my project I'd like to support the extended features. As a step in that direction, I updated my local build process to patch
bindings/src/lib.rsto use this line instead:This proved insufficient, however, as other changes appear to be needed. For example, the exported
Ingredientclass lacks thealiasattribute that would be populated by the extended parser.Could the bindings be updated to make the extended parsing available?