flamingo-commerce icon indicating copy to clipboard operation
flamingo-commerce copied to clipboard

Flexible E-Commerce Framework on top of Flamingo. Used to build E-Commerce "Portals" and connect it with the help of individual Adapters to other services.

Results 63 flamingo-commerce issues
Sort by recently updated
recently updated
newest added

Because of swaggo/swag#721, we have excluded the `docs` directory from the diff check of the testrecent stage. When the problem is fixed, we should remove the exclusion again.

Flamingo core offers an easy way of adding metrics and tracing. Currently we barely expose metrics and traces inf flamingo-commerce. This could be improved in the future.

enhancement
v4

The current in memory behaviour stores all data in the memory. To enable people to use flamingo-commerce without a cart backend we should rework this behaviour. We could rename it...

enhancement
v4

Hello friends, we noticed we sometimes have inconsistencies in our flamingo cache compared with the source of our adapters for the cart. Let us look at the `addProduct` function: ```...

help wanted

Hello friends, the handling of events has changed since this PR: https://github.com/i-love-flamingo/flamingo-commerce/commit/650f15f00af5799dc2779165c785bbf4341ffbc0 The events `ChangedQtyInCartEvent` and `AddToCartEvent` have been adjusted to match the event handling for deferred events of the...

enhancement
good first issue

The service should be independent of session since it belongs to interface layer. Currently the CartService can only be used in a controller context. In the future it should be...

enhancement
v4

Currently we use different wording for the same thing. ApplyVoucher adds stuff to the AppliedCouponCodes. We should rename the Actions in the controller so that Voucher will become CouponCode.

v4

Besides a session based cache a other backend would be nice since session based caching can lead to race conditions. Issues is up for discussion.

enhancement
v4

BEfore placing order there might be the need to do a (more strict) Validation. Idea: - Inject a optional "tagged" cartvalidator in the cartservice (e.g. tagged with "placeorder") - Offer...

We should change the Attributes similar to category attributes. Product -> n Attributes -> n Attributevalues In graphQL Types also

v4