Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/vuejs/vue/issues/3135 below:

Null prop value now interpreted as a value, rather than null, meaning the default isnt used. · Issue #3135 · vuejs/vue · GitHub

Hi,

1.0.25

http://jsfiddle.net/st5bak15/2/

This break occurred after upgrading to 1.0.25. It worked as (I) expect in 1.0.24 and below...

Previously I was defining a prop value on a component as either a json object, or null, depending on whether it was defined or not.

In the case of the prop value being null, Vue would default to using the defined prop default from the component, rather than explicitly null.

However, now the opposite is happening. When null is sent in as the prop value, the prop value remains as null, rather than being recognised as null and then loading up the default value.

Not sure if this was an intended change or not but thought Id highlight it as it has broke my app.

Cheers
Lee

JosielFaleiros, ninahaack and gadelkareem

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4