bean and property atrributes should be optional if value is provided
- Dominant language
- Groovy
- Stars
- 2.9k
- Forks
- 975
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 92
Description
On a few occasions I've wanted to use `f:display` to render a value which is not a bean property. Here's a contrived example
```
```
But the invocation of `f:display` without a `property` attribute causes an exception. I don't see why I should need to provide either a `property` or `bean` attribute when I'm specifying the field value like this?
Contributor guide
Research direction
Start by locating the f:display tag implementation and the related f:with usage shown in the issue. Reproduce the example with value="${cb.calc()}" and no property or bean attribute; done means the value renders without the current exception while existing property- and bean-based uses continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100