Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add build fixups + use Artifacts #13
Add build fixups + use Artifacts #13
Changes from 3 commits
093c15a
f9b3e08
4d8f0da
58e44e5
75790fe
b4e89dd
a6904cd
751dbc9
6fddbfe
53ac134
025e861
f6ede40
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a lot of manual fix-ups, it would be nice to follow up on creating PR in the
dash
repo so we can remove each of these one by one. We can create Issues here to track it potentially ?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point!
I would start by opening an issue in https://github.com/plotly/dash/issues mentioning that the "proper" way (and the one that's work with
PackageCompiler.jl
😏 ) to handle artifacts in Julia now is by definingArtifact.toml
.Then, we should mention that
Artifact.toml
only accepts tarball, so we would need to tar themin.js
andmin.js.map
files together in the build process so that the tarball is part of the npm registry and has a permanent URL available from unpkg.comWe could also reference this PR (they can see it, it's opensource 🎊 ) to put things in context.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we actually need these
externarl_url
definitions now that we're set to use Artifacts and a tarball?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, we didn't need them before since they never actually worked 😏
If we're going to have an external_url resource, it'd be nice if it was a functioning link even if we won't rely on it because of artifacts.
Maybe there's a case where artifacts can't be acquired and this would be the fallback ?