Want to override ProductBundle's validation.yml

I want to override ProductBundle’s validation.yml to allow validation for a 3rd product type, “giftcard”.

YAML

Oro\Bundle\ProductBundle\Entity\Product: properties: type: - NotBlank: ~ - Choice: { callback: getTypes }

1 2 3 4 5

Oro\Bundle\ProductBundle\Entity\Product:     properties:         type:             - NotBlank: ~             - Choice: { callback: getTypes }

I have tried these but it still have a violation of product type not being valid:

Trial 1:

YAML

Oro\Bundle\ProductBundle\Entity\Product: properties: type: - NotBlank: ~ - Choice: choices: [simple, configurable, giftcard]

1 2 3 4 5 6

Oro\Bundle\ProductBundle\Entity\Product:     properties:         type:             - NotBlank: ~             - Choice:                 choices: [simple, configurable, giftcard]

Trial 2:

YAML

Oro\Bundle\ProductBundle\Entity\Product: properties: type: - NotBlank: ~ - Choice: groups: [simple, configurable, giftcard]

1 2 3 4 5 6

Oro\Bundle\ProductBundle\Entity\Product:     properties:         type:             - NotBlank: ~             - Choice:                 groups: [simple, configurable, giftcard]

Please advise what am I doing wrong or if there is a way to replace that callback function with my custom array?

We want to avoid overriding the Product Entity with another custom type. Thanks.

Topic

[ShahriarParticipant]

Just to clarify, the First screenshot is how validation.yml is set in Oro’s ProductBundle.

The Trial screenshots are how I tried to overwrite from my own custom bundle’s validation.yml.

• This reply was modified 4 years, 6 months ago by  Shahriar.

[Andrey YatsenkoModerator]

You can override it with the validation groups. But you should note that there is a lot of code that relies on the fact that there are only two types of products at the system, so it can be hard to override other parts, as this functionality is not intended to be extensible.

[Author]

Replies