QualiSystems / QualiSystems/shellfoundry
add driver validations - compare to the driver metadata
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 19
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
Issue details
When the driver metadata is refering to commands that do not exist in the driver.py, end with a relevant error the pack/install commands of the shellfoundry to prevent issues later on (commands will not be available, etc).
Steps to reproduce
have a few commands in the driver.py and more/different commands in the driver metadata file.
run shellfoundry pack
return errors about missing commands (ones that exist in the metadata and not in the driver.py - the other way is ok)
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 shellfoundry pack and install commands, then locate how driver.py and the driver metadata file are loaded. Compare metadata commands against commands defined in driver.py and verify that missing commands produce an error during packing or installation, while the reverse mismatch remains allowed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100