posit-dev / posit-dev/py-shinylive
Use `SHINYLIVE_ASSETS_VERSION` envvar to control assets version in export
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 56
- Forks
- 6
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
In R, we have assets_version() that uses the default (hard-coded) assets version but also consults the SHINYLIVE_ASSETS_VERSION envvar. We should replicate that with py-shinylive. Doing so makes it easier to move between asset versions, improves testing and decouples py-shinylive package releases from the shinylive releases (which do need to be updated with py-shiny releases).
Note that not all assets versions will be compatible with all shinylive versions.
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
Start by locating the py-shinylive export entry point that selects the assets version, then compare its behavior with the R assets_version() behavior described in the issue. Done means the export honors SHINYLIVE_ASSETS_VERSION while retaining the existing default and accounting for the stated compatibility caveat.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100