Skip to content
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

fix: Import of custom Superset assets #881

Merged
merged 2 commits into from
Jun 21, 2024
Merged

Conversation

bmtcril
Copy link
Contributor

@bmtcril bmtcril commented Jun 21, 2024

The custom Superset assets are all pushed into a single assets.yaml file, and need to be separated by --- lines. This fixes the ability to read multiple custom assets from the assets.yaml / superset-extra-assets patch.

Also allows the import_superset_zip command to serialize assets to other locations so that extensions can use it as well.

@bmtcril
Copy link
Contributor Author

bmtcril commented Jun 21, 2024

@pomegranited you'll need this fix to use custom assets. My tests for this are here: https://github.com/bmtcril/tutor-contrib-aspects-extension

bmtcril added a commit to bmtcril/tutor-contrib-aspects-extension that referenced this pull request Jun 21, 2024
Previously the commands and helpers that we use to ensure various things import correctly only worked for Aspects itself. However extension developers will need to do this for their assets as well, so this lets us choose where to write the processed assets to.
@bmtcril
Copy link
Contributor Author

bmtcril commented Jun 21, 2024

@Ian2012 this could use a re-review whenever you have a min.

@Ian2012 Ian2012 merged commit 6335724 into main Jun 21, 2024
9 checks passed
@Ian2012 Ian2012 deleted the bmtcril/fix_custom_assets branch June 21, 2024 20:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants