spring-projects / spring-projects/spring-boot

Investigate simplifying WebMvcAutoConfiguration if templating isn't being used

Open
#17,354 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: pending-design-work type: enhancement
Dominant language
Java
Stars
81.5k
Forks
42.7k
Avg merge
2d 4h
Merged PRs (30d)
65

Description

See #16953 for background:

WebMvcAutoConfiguration currently configures a lot of components that are specific to use of Spring MVC with a templating engine to produce server-side generated text/html content.

We repurposed #16953 to deal with HiddenHttpMethodFilter, but there may be more that we can do.

Contributor guide

Open the contributing guide

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.

Research direction

Start by reading WebMvcAutoConfiguration and the background in issue #16953, including the discussion of HiddenHttpMethodFilter. Investigate which configured components are specific to templating-based server-side content, and consider the work complete when a concrete simplification scope and its expected behavior are established.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring-boot
Domain
backend, web-dev
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.