-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Change default behaviour for R package generator to recycle package version info #870
Comments
Let's take a step back here - AFAICT this version is just used in the cache-busting query param when we generate a Is there really any reason we need both of these? Once we have mod time - which supports changes during development as well as users upgrading versions - isn't the version redundant? I propose we simply get rid of version and only use mod time. |
From my point of view, I think 🔪 the I've yet to run into any generated packages/libraries which contain assets where (a) the asset version ≠ the package version, and (b) it's important to maintain this distinct version information. |
Speaking of which, can I introduce a simple PR to 🔪 |
In |
🎉 This issue was resolved in #1048. Closing! |
Currently, the R package generation code inserts an integer (which increments for each additional asset inserted into the dependency list) for the version number when none is available in
__init__.py
.It would be safer to default to inserting the same version information as for the containing package, since this currently requires developer intervention and editing of
internal.R
after the package is generated. A (fictional) example:This is important because of the way Dash dependencies are currently fetched via URL:
https://github.com/plotly/dashR/blob/a44050a27ba55056afed8ebac81e852ddf852e1f/R/utils.R#L196-L204
I propose that the default should be to replace
version = "1"
andversion = "2"
withversion = "2.0"
in the example above if version information for dependencies is not available within a generated package.The relevant code block is here:
dash/dash/development/_r_components_generation.py
Lines 278 to 286 in d9ddc87
@alexcjohnson
The text was updated successfully, but these errors were encountered: