client side code generation from openapi/swagger specification

Open
#280 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java, openapi
Domain
devtools, tooling

Research direction

The issue names no files, tests, or entry points. Start by reviewing the existing server-side generator and the OpenAPI/Swagger generation path; clarify supported client languages and build environment before implementation, with done defined by an agreed client-side generation scope.

Written by the indexing model from the issue text.

Description

enhancement help wanted

Currently only server side code generation is supported.
This issue is to discuss topics and todo's (e.g. supported languages, build environment etc)

Dominant language
Java
Stars
49
Forks
25
No merged PRs in 30d

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.

More from networknt/light-codegen

All issues in networknt/light-codegen

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.