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
The message for missing properties could be more developer-friendly.
Today, if you have a class Foo with a method getBar(boolean paramName), when you try to use "foo.bar" in an EL expression Flavour produces a build-time error like this:
Can't find property 'bar'
It is technically correct. Per the JavaBean spec, the "bar" property is only readable if there is a no-arg getter, like getBar().
Ideally Flavour would find other methods with the same name but with parameters and warn about the potential confusion:
Can't find property 'bar'. Only a no-arg getter can be used to get 'bar'. These getter(s) exist but have parameters, so they can't be used: getBar(boolean)
The text was updated successfully, but these errors were encountered:
The message for missing properties could be more developer-friendly.
Today, if you have a class Foo with a method getBar(boolean paramName), when you try to use "foo.bar" in an EL expression Flavour produces a build-time error like this:
Can't find property 'bar'
It is technically correct. Per the JavaBean spec, the "bar" property is only readable if there is a no-arg getter, like getBar().
Ideally Flavour would find other methods with the same name but with parameters and warn about the potential confusion:
Can't find property 'bar'. Only a no-arg getter can be used to get 'bar'. These getter(s) exist but have parameters, so they can't be used: getBar(boolean)
The text was updated successfully, but these errors were encountered: