Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Template migration fails when using optional chaining operator in templates #397

Open
Tallyb opened this issue May 31, 2024 · 2 comments · May be fixed by #409
Open

Template migration fails when using optional chaining operator in templates #397

Tallyb opened this issue May 31, 2024 · 2 comments · May be fixed by #409
Assignees
Labels
bug Something isn't working

Comments

@Tallyb
Copy link

Tallyb commented May 31, 2024

x is an input transformed to signal.

The template has a "something = x?.y"

expected the template to change to "x()?.y". but it does not migrate.

@eneajaho
Copy link
Collaborator

eneajaho commented Jun 6, 2024

Hello @Tallyb
Thanks for opening this issue. Will check it out later this week.

@eneajaho eneajaho added the bug Something isn't working label Jun 6, 2024
@eneajaho eneajaho self-assigned this Jun 6, 2024
@ilirbeqirii
Copy link
Contributor

@Tallyb I had a similar issue with optional chaining in the template, but for me, the problem was that the template was not properly formatted, and the interpolation expression had bad formatting, i.e. having space before and after, like the following:

<span>{{
project?.title ? project.title : ""
}}</span>

If possible, can you please provide more info (more piece of code) about the problem you had?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
3 participants