Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Allow endpoints to be turned off with a property

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java, spring
Domain
api, backend

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.

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.

Dominant language
Java
Stars
2
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from BroadleafCommerce/spring-frameworkmapping

All issues in BroadleafCommerce/spring-frameworkmapping

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.