swagger-api / swagger-api/swagger-codegen
[Erlang] Enhancements to Erlang server generator
Open
Nobody has claimed this yet.
Enhancement: General
help wanted
Server: Erlang
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
- Write specs for static exported fuctions
- Write specs for generated exported fuctions
- Add datetime/date validation
- Separate gigantic
apito submodules and refactor the routing - Add tests for the validators
- Add integrational test for the whole cycle
- Add validations of definitions with inheritance
- Add proper response validation (this
listhack is so weird) - Fix enum validation. It doesn't work correctly when the parans is in qs/header
Swagger-codegen version
Latest master (Sep 2016)
If anyone wants to work on any of these tasks for erlang-server, please reply to let us know.
Ref: https://github.com/swagger-api/swagger-codegen/pull/3758
cc @galaxie
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 the erlang-server generator and the related pull request at https://github.com/swagger-api/swagger-codegen/pull/3758. Break the checklist into a defined task, then inspect the existing generated API, validators, and integration cycle before deciding what tests are needed. Done means the selected validation, specification, routing, or testing gap is addressed without taking on the entire list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- backend, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100