Clarify costs rule names/scopes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 148
- Forks
- 55
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 18
Description
Feature Request
We have the following rules:
build_cost_databuild_fuel_pricesretrieve_cost_data_usaretrieve_cost_data_eurretrieve_eia_data
From a naming perspective, it is not entirely clear what the differences are. For example, some fuel costs come from build_cost_data if using the ATB, while others are created in build_fuel_costs if they are dynamic. Clarity on scope and name would be good!
Suggested Solution
No response
Additional Info
No response
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
Locate the definitions and usages of build_cost_data, build_fuel_prices, retrieve_cost_data_usa, retrieve_cost_data_eur, and retrieve_eia_data, then compare their scopes and the ATB versus dynamic fuel-cost paths. Done means the rule names and their scopes clearly distinguish these behaviors and the affected references remain consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100