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.
⬆️ not yet.
Looking to fix #19
I've done research on what I want happening vs what the current Assets APIs are, but could use some guidance from here on whether this PR direction is making architectural sense.
N/A
I want to reach something like this
I want this to auto-dequeue external asset if
canEnqueue()
doesn't pass.I still need to implement External{Script,Style}, but thought I'd post what I have at the moment.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Hopefully not.
Other information:
What are your thoughts about how this idea is looking?