use nextLoad().format rather than context.format #224
Merged
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
|
at least one test needs to be added but I believe this PR has the solution |
koshic
approved these changes
Aug 7, 2023
Yep, it looks like a good solution - next loaders (or default loader) must provide format on their 'load' hook. Only one [rare] case probably not covered - when some loader added into the chain after esmock, format returned from that loader will be ignored. |
|
@koshic thanks |
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.
re #224
context.formatis not always defined andnextLoad().formatis always defined and usingnextLoad().formatallows the test to pass