Implement customer specific data in javascript component

[tdgroot]

This fixes #20 and part of #8.

I got rid of all the customer specific code in the module and re-implemented the code in a javascript component. One customization had to be made by adding a plugin, which adds a few variables to Customer CustomerData like:

• id
• group_id
• group_code

While wrapping up the changes, I ran the tests, they all succeeded. Doesn't mean much though, as there are just a few tests 😅.

All the code concerning customer data has been removed or refactored, so it would be wise to upgrade the version to 0.3.

I known it's quite a bold PR, but I think this is the best way to get around the customer data problems. If you have some suggestions, please let me know.

[jissereitsma]

Awesome work! I don't have much time to invest in this, but I can see that the JS component looks clean. Especially the usage of the sectionData change to add the right GTM information to the customerData.get('customer') was one I envisioned already and to see it being implemented by someone else is extremely cool. Many thanks!

The only but I have is that I have become wary of releasing new versions, modified through third party PRs, without actually checking things thoroughly. For this, I have on my list to create various unit tests, but more importantly integration tests (Codeception) to guarantee the right behaviour. Do you object against postponing the release?

[tdgroot]

Thank you for merging, great to hear that you like it!

As of the postponing, I completely understand. You're the project maintainer after all!

Good luck with writing the tests, I'm very interested :).