Changes for issue #43 (Shortcut for multiple object properties)

[anikolaev]

Changes for issue #43 :

• add mapObjectFields() to add object properties using template e.g. 'property.*' or '*'

[coveralls]

Coverage remained the same at 100.0% when pulling 58eca7f on anikolaev:object-prop into 65842ca on maoberlehner:master.

[maoberlehner]

@anikolaev thank you for your work! I'll take a closer look the next couple of days. Sorry for the delay, I've got a lot of stuff to do currently.

[mariobalca]

Hey @maoberlehner, sorry to bother but this actually seems to be the perfect solution for some difficulties that I'm having using vuex-map-fields, do you have an estimation of when is this getting merged/released? And thank you for your work with this package, it's really helpful!

[code-yo]

@maoberlehner thanks for the great package it's very simplify my way in project. But I have the problem with fields that does not exist. Could you please review and merge pull-request?

[maoberlehner]

Please revert the yarn.lock file. Thx!

Additionally, I find it confusing that the API of mapObjectFields() and mapFields() is pretty much the same. I'd find it hard to explain that in the documentation. Btw: please also update the documentation in the README.md ;)

I'd love to have the functionality from mapObjectFields() merged into mapFields() if this is possible?

Thanks for the great work so far!

[anikolaev]

@maoberlehner One of previous yarn versions added these integrity lines. Now they only add them for changed modules. Reverted.

Yes, I think integration of mapObjectFields() into mapFields() may work but it needs to be investigated. I see at least one limitation - you cannot have keys with asterisks (*) in this case but they are probably rarely used. Same for empty keys. Maybe mapMultiRowFields() also could be integrated (something like ...mapFields({ users: 'users[]'})). Unfortunately I am not sure I can check it now. Same for the documentation.

[Exalyn]

Hi.
I'm using your work and i found this, any update or news about this feature ?
I have a user form with a separate address component including billing and shipping address, so mapping all fields is kinda long and not very good.

[frankievx]

Can someone revert the yarn.lock?

[geoidesic]

@anikolaev looks like there are failing tests here. Can you address this?