core: move ES module path into FrontendMetadata
#2317
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.
Summary:
The two loading mechanisms are now specified in the same data object, so
switching from one to the other requires only a single change.
The HTTP API and the frontend are unchanged.
Test Plan:
Modify the scalar plugin’s
frontend_metadata
to use an ES module path:Then, launch TensorBoard and note that the
plugins_listing
responsecontains the right values for both the scalar and image plugins.
wchargin-branch: es-module-metadata