spring-projects / spring-projects/spring-data-rest
Create XML namespace that controls which repositories are exported [DATAREST-1]
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 958
- Forks
- 568
- PR merge metrics
- No merged PRs in 30d
Description
Mark Pollack opened DATAREST-1 and commented
The user should be able to select a subset of the Spring Data Repositories that are exported. Also, the user should be able to export subset of the full CRUD Repository functionality. An example would be to export only read operations. There could perhaps be a tie-in as well with security, a person who is authenticated with an admin role would have access to full CRUD, where as other roles would be more readonly. Might need a seperate JIRA issue to discuss how security could be either demoed in the sample or more dedicated support for ease of use/configuration provided
No further details from DATAREST-1
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
Start by locating the XML namespace configuration and the Spring Data Repository export entry points. Define how users select repositories and expose only selected CRUD operations, then verify that the behavior can support the described read-only and full-CRUD cases; security integration is noted as potentially separate work.
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
- 20/100