Nuxt•2y ago•

18 replies

Nuxt ignores boolean logic

I've encountered a bizarre and infinitely strange behavior in Nuxt3 (@3.8.0), and I don't even know how to describe it, but I've attempted to illustrate it with screenshots.

There are two divs using

v-if

v-if

and

v-else

v-else

directives, and Nuxt rendered both the

v-if

v-if

wrapper and the content from the

v-else

v-else

block simultaneously. This should be physically impossible, as boolean logic implies either displaying the

v-if

v-if

block or the

v-else

v-else

block, but not displaying the

v-if

v-if

block with content from the

v-else

v-else

block.

Please, explain to me how this could have happened and what's under the hood of Nuxt3 to allow such behavior?

Important note:
As you can see in the screenshots, the

v-if

v-if

section and the content of

v-else

v-else

depend on the computed variable

role

role

. After rendering, the

role

role

variable changes in a way that it no longer satisfies the condition from

v-if

v-if

, but it starts satisfying the condition for displaying the content inside

v-else

v-else

.

Expected behavior: upon changing the

role

role

variable, the

v-if

v-if

section is ignored, and only the

v-else

v-else

section with the corresponding content is used.

@moderator I apologize to the moderators for the ping, but the issue appears to be critical.

Nuxt•2y ago•

18 replies

Termonna

Nuxt ignores boolean logic

I've encountered a bizarre and infinitely strange behavior in Nuxt3 (@3.8.0), and I don't even know how to describe it, but I've attempted to illustrate it with screenshots.

There are two divs using

v-if

v-if

and

v-else

v-else

directives, and Nuxt rendered both the

v-if

v-if

wrapper and the content from the

v-else

v-else

block simultaneously. This should be physically impossible, as boolean logic implies either displaying the

v-if

v-if

block or the

v-else

v-else

block, but not displaying the

v-if

v-if

block with content from the

v-else

v-else

block.

Please, explain to me how this could have happened and what's under the hood of Nuxt3 to allow such behavior?

Important note:
As you can see in the screenshots, the

v-if

v-if

section and the content of

v-else

v-else

depend on the computed variable

role

role

. After rendering, the

role

role

variable changes in a way that it no longer satisfies the condition from

v-if

v-if

, but it starts satisfying the condition for displaying the content inside

v-else

v-else

.

Expected behavior: upon changing the

role

role

variable, the

v-if

v-if

section is ignored, and only the

v-else

v-else

section with the corresponding content is used.

@moderator I apologize to the moderators for the ping, but the issue appears to be critical.

Nuxt ignores boolean logic

Similar Threads

Nuxt ignores boolean logic

Similar Threads

Similar Threads

Similar Threads