You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In [email protected] and prior, a component invoked in block form like {{#pkg::component-name}} would be looked up via the resolver as pkg::component-name.
Starting with beta.3 with the upgrade to [email protected], that name is normalized via customizeComponentName to become pkg/component-name. For a customized resolver where :: is a meaningful token, such components no longer resolve correctly.
🔬 Minimal Reproduction
The following is resolved as component:pkg::component-name in beta.2, but component:pkg/component-name in beta.3:
🐞 Describe the Bug
In
[email protected]
and prior, a component invoked in block form like{{#pkg::component-name}}
would be looked up via the resolver aspkg::component-name
.Starting with
beta.3
with the upgrade to[email protected]
, that name is normalized viacustomizeComponentName
to becomepkg/component-name
. For a customized resolver where::
is a meaningful token, such components no longer resolve correctly.🔬 Minimal Reproduction
The following is resolved as
component:pkg::component-name
in beta.2, butcomponent:pkg/component-name
in beta.3:Note that an inline invocation like
{{pkg::component-name}}
does not go throughcustomizeComponentName
and so still resolves as before.😕 Actual Behavior
Block curly component names have
::
normalized to/
.🤔 Expected Behavior
Block curly component names aren't subjected to the same normalization rules as angle-bracket components, as in prior releases.
🌍 Environment
➕ Additional Context
Additional discussion of the details of this issue is at glimmerjs/glimmer-vm#1255
The text was updated successfully, but these errors were encountered: