spring-projects / spring-projects/spring-grpc
POJO gRPC controllers - schema check on startup
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 413
- Forks
- 95
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 2
Description
Assuming we implement #122 (or some variant of that).
I think it would be neat, like Spring GraphQL does, to print out on startup a report of where the POJO component model differs from the schema provided so that the implementer would know where they've inadvertently strayed from a contract
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 reviewing issue #122 and its proposed POJO component model, then identify how the provided schema can be compared with that model during application startup. Done means producing a startup report that clearly identifies where the POJO model differs from the schema.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, java, spring-boot
- Domain
- api, backend, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100