New ComponentApiManager module to handle ComponentApi versions
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 6
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This module handle all the compatible version of the ComponentApi.
We will configure a range of required MAJOR version of the ComponentAPI.
When the server start, this module will then browse the Github Release of the ComponentAPI project to get the last MAJOR.MINOR.PATCH version of each MAJOR version. Then it will create a new ComponentApiLoader for each MAJOR.MINOR.PATCH version.
When an app validation is requested, the ComponentApiManager module will get the asked file from the given MAJOR version.
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are named. Start by locating the existing ComponentApiLoader and the app-validation entry point, then determine how configured MAJOR versions and GitHub releases are represented. Done means the manager selects the latest patch release for each configured MAJOR version, creates loaders, and serves the requested file for validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100