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

[native_assets_cli][native_assets_builder] Dry run dependencies & dry run caching #1321

Closed
dcharkes opened this issue Jul 11, 2024 · 1 comment
Labels

Comments

@dcharkes
Copy link
Collaborator

Dry runs don't have to report dependencies right now. The rationale being that no assets are being built, and if for example some native compilation is happening a dry run should not be concerned about

However, we could consider the 'dependencies' of a dry run to be the files that are required to come up with the list of assets. Then we could cache dry runs.

I'm not entirely sure what this will look like once we nest dependencies inside assets though:

@dcharkes
Copy link
Collaborator Author

@dcharkes dcharkes closed this as not planned Won't fix, can't repro, duplicate, stale Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant