Automatically generate HTML assets in the output directory to simplify the configuration #390
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gcrabbe
force-pushed
the
config-assets
branch
from
d21c011 to
49a4ee9
Compare
JasperCraeghs
changed the title
JasperCraeghs
approved these changes
Dec 30, 2024
Letme
approved these changes
Dec 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Register a callback for automatically copying local Javascript resources to the output
_staticdirectory in order to simplify the configuration.Inspired by the Sphinx tutorial.
Generate
hyperlink_colors.cssdirectly in the output_staticdirectory instead ofmlx/traceability/assetsfirst. Adding files to the package was a bad idea aspip uninstall mlx.traceabilitydoesn't clean it up and it can cause permission errors.