wipe back-end build artifacts before creating new ones
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24.4k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 13
Description
Not quite sure if this issue should be resolved in the component generator or in the component boilerplate, but when we're generating new Python/R/Julia files we should find a way to wipe the old ones first. Otherwise certain changes can leave obsolete files hanging around:
- If you change the R/Julia prefixes
- If you change the name of a component
- If you delete a component.
came up in https://github.com/plotly/dash-vtk/pull/6/files#r565645444
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 reviewing the component generator and component boilerplate, using the linked dash-vtk pull request discussion as context. Trace how generated Python, R, and Julia files are created, then determine how stale files should be removed after prefix or component-name changes and component deletion. Done means obsolete generated files no longer remain after regeneration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia, python, r
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100