Make API for exporting JS content more explicit #4333
Merged
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.
This PR brings the improvements to the
export
function from #4258. Having this change will make implementing another PR easier, so I wanted to make a separate PR for them now.Change:
export
function supports. It is the responsibility of the caller to ensure the string matches the contract laid out by theExportJs
type. The makes theexport
function a lot more explicit and easier to change.This PR is purely internal refactoring and doesn't affect the generated JS in any way.