Need to support multiple versions
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 0
- Forks
- 7
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 2
Description
Currently flix only has one version (1.0.0)
Soon there will be version 1.1.0, need an approach to managing multiple versions. Some thoughts:
(strict)Force flix to be migrated to newest version before they can be executed or bindings generated(lax)Have version specific logic for executing and generating bindings files (might not be much specific logic needed from version to version)(mixed)Allow executing all versions and only support generating binding files on current version. Then users would only have to migrate flix to generate binding files.(kick can)Decide later and only support current version at development time.
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
Start by reviewing how flixkit-go currently handles the single Flix version for execution and binding-file generation. Compare the strict, lax, mixed, and deferred approaches described in the issue; done requires choosing and implementing a clear strategy for managing multiple versions, including the planned 1.1.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100