Should vuex mapState print error message #1093 #1162

[EdyHartono]

• return an empty array when map is not valid
• log an error message when map is not valid

[EdyHartono]

@ktsn i don't know if i should directly throw an error in non production mode or just log the error, any suggestion ?

[joachimboggild]

I think it would be nice if it threw an error. As far as I can see, if a developer is not providing the proper values, he is making a mistake, and it would be a bigger help to actually have this exception being thrown, because it would be more noticeable.

Another small suggestion for this phrasing:
"[vuex] states parameter must be either an Array/Object"

It might sound better with
"[vuex] states parameter must be either an Array or an Object"
or
"[vuex] states parameter must be Array/Object"

"either" sounds a bit strange together with the "slash" phrasing.

... just my two cents :-)

Thanks for doing awesome work.

[jamescostian]

This PR would have saved me an hour today if it were merged. Is there any reason why it hasn't been merged? It's a fairly small and simple PR and it provides Vuex users with much better feedback than is currently provided when you make a mistake with mapState

[sustained]

Also wondering why this wasn't merged.

[ktsn]

LGTM. Thank you!

[vue-bot]

Hey @EdyHartono, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚