Skip to content

Wrapped in an if-clause and bound regex pattern is modified and if-clause property is toggled #169

@notmessenger

Description

@notmessenger

The resolution of #161 introduced this bug. When {{ef-element-error}} is not wrapped in an {{#if}} all works as expected. When it is wrapped in an {{#if}} and

  • If condition is initially false, not displaying this component
  • The if condition is toggled to true
  • The bound error pattern of this component is changed to one that still matches.
  • The bound error pattern of this component is changed to one that does not match.
  • The default instance of this component will display its content because there are no pattern matches in any of the other instances.

but

  • If condition is initially false, not displaying this component
  • The if condition is toggled to true
  • The bound error pattern of this component is changed to one that still matches.
  • The if condition is toggled to false
  • The if condition is toggled to true
  • The bound error pattern of this component is changed to one that does not match.
  • The default instance of this component will NOT display its content even though it should because there are no pattern matches in any of the other instances.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions