Enhance Frogbot To Account for Packahe Manager and/or Language Inputs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 107
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 5
Description
Currently, it seems like I have to build out the propper components for Frogbot. I should be able to reference this via the use of a JF_FROGBOT_PACKAGE_MANAGER, for python there are several ways people manage packages, and the package handlers should account for this. The same goes for Java and Javascript. (yarn, npm, gradle, maven, etc). Right now the package-manager handlers do no justice to individuals consuming Frogbot. Frogbot should be able to traverse the structure and tell me what kind of package it is, but there should also be an overwrite input as well for the language it should scan JF_FROGBOT_PACKAGE_LANGUAGE, which should also help the scan be significantly faster than what it currently does in terms of it's functionality.
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 tracing the package-manager handlers and the existing configuration inputs, especially JF_FROGBOT_PACKAGE_MANAGER and JF_FROGBOT_PACKAGE_LANGUAGE. Compare the expected Python, Java, and JavaScript package-manager cases, then define how repository traversal and the language override should behave before implementation. Done means the supported package types and override behavior are specified and verified by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, javascript, python
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100