mamazu
mamazu
Yeah this makes much more sense. We just need to copy over the route config from the admin bundle and we are basically done.
Building another filter based action (despite the fact that we have all of the features in the resource bundle) doesn't really make sense, in my opinion. If we'd build something...
I have implemented a very straight forward approach under the assumption that if the channel can not be found then the route does not exist (in our case this means...
Hello, I have checked the error out. Neither endpoints have any validation on those properties. This is the reason you are getting a 500 error from this endpoint. (Which is...
It already does. If you are giving it a code it will take that provinceCode into account. But if you don't do that or you just give it the name...
Reusing the shop bundles code is not a good idea as this would mean that the headless approach of the api still needs another front-end to work. But the reason...
This bundle is decoupled as far as I know from the shop package. And the class that you are refering to is from the core bundle (ShopUser) and the route...
Because if the customer is trying to order with an existing email address then the customer has to log in, there is no way around it otherwise it would be...
Sure there could be documentation on how to check if an email exists and how to implement such an endpoint.
Just talked to @lchrusciel and he said that this is a feature we should do but not in the 1.0 release.