BroadleafCommerce / BroadleafCommerce/spring-frameworkmapping
Allow endpoints to be turned off with a property
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
We might be able to resolve this with some clever property bindings where the property name is the class name of the controller. That would be better than being required to annotate every controller with @ConditionalOnProperty.
In all scenarios, autocompletion should work with these properties.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing how Spring Web request mappings discover controllers and how property bindings could use controller class names instead of requiring @ConditionalOnProperty on each controller. Done means endpoints can be turned off through properties and those properties support autocompletion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100