Contradictions from no-potential-path-strings and no-unnecessary-curly-strings

[ijlee2]

I'd like to pass a string that starts with @ to an argument:

<Ui::Demo @title="@my-org/my-package">
  ...
</Ui::Demo>

In ember-template-lint@v5, the code above caused no-potential-path-strings to fail. So I used double curly braces to avoid false positives.

<Ui::Demo @title={{"@my-org/my-package"}}>
  ...
</Ui::Demo>

In ember-template-lint@v6.0.0, using double curlies for string causes no-unnecessary-curly-strings to fail. And without double curlies, no-potential-path-strings still marks the code as an issue.

error  Potential path in attribute string detected. Did you mean {{@my-org/my-package}}?  no-potential-path-strings

Could either/both rule(s) be reviewed for accuracy and/or relevance?

[ijlee2]

Looking at #1457, I feel like no-potential-path-strings had been added to account for rare cases.