spring-projects / spring-projects/spring-data-mongodb
Add `@Meta(resolver = …)` attribute to customize `Meta` resolutions
Open
Nobody has claimed this yet.
theme: 5.1
- Dominant language
- Java
- Stars
- 1.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
In the discussion of potential solutions for #4808, one idea was to add a resolver attribute to the @Meta annotation that could…
- either take a SpEL expression returning a fully populated
Metainstance to be used for the query execution - or refer to a named bean implementing a dedicated interface
MetaResolver.resolve(RepositoryMethodContext)so that implementations get access to the full method
I guess both could be supported at the same time, but we might end up adding only one of the options.
Contributor guide
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
The issue points to discussion #4808 and the @Meta annotation, but names no files or tests. Start by reading #4808 and tracing Meta resolution in repository query execution; completion would require choosing and defining the supported resolver approach, including how the SpEL option or MetaResolver.resolve(RepositoryMethodContext) is handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, mongodb, spring
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100