Improve form designer
Open
BACKEND
- Dominant language
- Kotlin
- Stars
- 25
- Forks
- 6
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 9
Description
Now all field types share the same settings. The available properties should depend on the type of the input
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Locate the form designer and inspect how field types currently share settings before determining where type-specific properties are defined. Done means each input type exposes only its applicable properties, with the behavior verified in the existing form-designer flow.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100