Updates is_wildfire column name to "label"
Open
Nobody has claimed this yet.
endpoint: sequences
module: models
- Dominant language
- Python
- Stars
- 29
- Forks
- 14
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 5
Description
Thanks to #497 the is_wildfire column is more explicit allowing finer labelisation.
However, from now on, the name of the column is ambiguous. Indeed, the name is_wildfire makes one think of a boolean which is not anymore.
Would the name "label" more convenient ?
What do you think ?
Happy to discuss it !
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
Search the repository for every reference to the is_wildfire column and review how the schema and API expose it. Rename the column to label consistently, account for any database migration or compatibility impact, and verify that relevant tests and API behavior still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi, postgresql, python
- Domain
- api, backend, databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100