[improvement] remove flowkit as a dependency
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 0
- Forks
- 7
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 2
Description
Issue to be solved
Whenever there is an update to flowkit it causes more dependency issues. I'm sure why flowkit is necessary in this repo.
Suggest A Solution
It would be nice to simplify and remove it. In this scenario the source (e.g. Flow CLI) would grab what it needs from flowkit and send it over.
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 tracing how this Go repository uses flowkit and how the Flow CLI currently obtains and sends the required data. Clarify which flowkit functionality is necessary before deciding how to remove the dependency. Done means dependency-related update issues are eliminated while the source can still provide everything the CLI needs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100