[HTMLExporter] Initialize resources before widget filtering #2118
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.
WidgetsDataTypeFilter
is responsible for outputting appropriate widgets code where needed. Ifresources
is passed to it, it looks inside forpath
andname
parameters to figure out where to find metadata. The defaultname
is"Notebook"
, set inExporter._init_resources
. However, inHTMLExporter
,resources
is passed toWidgetsDataTypeFilter
here, beforeExporter.init_resources
is called (indirectly here).This works ok as long as the default behavior for setting
name
is not needed - so all commandline conversions work. But when used programmatically (like here, for notebooksharing.space), this causes widgets to not be rendered, as thetext/plain
mime type is chosen each time.This PR explicicly calls
_init_resources
before instantiatingWidgetsDataTypeFilter
, so the defaulting behavior of_init_resources
is exercised.