pkf1994 / pengblog-ssm Goto Github PK

Version

2.6.10

Reproduction link

https://jsfiddle.net/dansebcar/b75n0uw6/16/

Steps to reproduce

• Press update to change each item's name to "b"

What is expected?

The list re-renders with the new name

What is actually happening?

The list does not change

---

If we instead define "symbol" as any non-empty string, the expected re-render is observed, so I think the cause is just the parent list (items) is accessed through a symbol.

Nesting the symbol property an additional level (IE in config, rather than directly on data) is necessary to render the list at all; I guess symbols from data aren't directly transferred?

I noticed in the devtools when I pressed "refresh" after mutating the items that I could see the new name, so I assumed something about the way I was setting the property didn't trigger the update, but even Vue.set did not help.

pkf1994/pengithub-vue#3
pkf1994/pengithub-vue#4

Environment

Vuetify Version: 2.1.9
Vue Version: 2.6.10
Browsers: Chrome 78.0.3904.70
OS: Linux x86_64

Steps to reproduce

Set text area to a value of null/undefined and render component using SSR mode.

Expected Behavior

Would expect null/undefined values to be not stringified and set as internal value.

Actual Behavior

null/undefined values appear to be stringified and set as initial value in SSR mode.

Reproduction Link

https://codesandbox.io/s/codesandbox-nuxt-vdcv8

Other comments

This is limited to how Vue is interacting w/ Nuxt SSR from what I can tell, originally I thought this was a Nuxt issue but they told me it isn't and to file it here instead. (pkf1994/pengithub-vue#3)

If I wrap the v-textarea component in client-only the problem disappears, definitely a SSR issue.
pkf1994/pengithub-vue#1
pkf1994/pengithub-vue#2
pkf1994/pengithub-vue#4
pkf1994/pengithub-vue#5