Mathias Rieder

Hi Boris, I did a fix based on that still pending branch that moves xtext version to 2.11 and ports Xtend-Richstring to back to jnario. Now I'm not really shure...

The issue here is, that the org.jnario.feature.jvmmodel.StepExpressionProvider copies the "implementation"-AST part from the Step that carries the original implementation. Adapters are not copied (and in fact its not really easy...

maybe it is also worth looking into haschmap-implementations that use case-insensitive hashing/equal to accomplish the case-insensitive lookups. options: - https://docs.rs/case_insensitive_hashmap/latest/case_insensitive_hashmap/ - https://docs.rs/unicase/latest/unicase/ It is not clear yet if something like...

hi @XLJ707781299 , thx for the issue first. Can you share a bit information about the size of your project (lines of code, number of files, compiler arguments ... stuff...

hey @corbanvilla, first of all, thx for your contribution. This PR is pretty big, and also the topics are quite new to rusty, so I guess we should discuss further...

what would you suggest to do instead of the panics? I dont think it is a good idea to just skip some things?!

Would we adding a diagnostic here that says: "Cannot do this & that. Please configure err123 as cirtical?". I even wonder if it is clear which ignore-rule lead to this...

Shall we rename the token/ast representation?

what are the circumstances where this is allowed? @ghaith do you know the rules here? assume ```st FUNCTION foo: VOID VAR_INPUT a, b, c : INT; END_VAR ... END_FUNCTION ```...

could you post some example ST code on how you would use this?