Akeneo merge validators instead of override
This question looks relevant, but it has not answer - Akeneo attribute validation issue
We have Category Validator
PimBundleCatalogBundleEntityCategory:
constraints:
- SymfonyBridgeDoctrineValidatorConstraintsUniqueEntity: code
- PimComponentCatalogValidatorConstraintsImmutable:
properties:
- code
I want ti remove immutable constraint. According to documentation I have to create new validator file, copy-past that code the new file and change what ever I want. But when I do this:
PimBundleCatalogBundleEntityCategory:
constraints:
- SymfonyBridgeDoctrineValidatorConstraintsUniqueEntity: code
or even this
PimBundleCatalogBundleEntityCategory:
constraints:
- SymfonyBridgeDoctrineValidatorConstraintsUniqueEntity: code
- PimComponentCatalogValidatorConstraintsImmutable:
properties:
- dummyField
it merges new validator with the original, so I can't remove immutable constraint from field "code".
I even tried to set empty array as a value of "properties". I tried to set "~" as a value, but it says, that "properties" should be array.
So, how to remove immutability from "code" field?
validation yaml immutability akeneo
asked Jan 18 at 16:03
HevywebHevyweb
2616
add a comment |
This question looks relevant, but it has not answer - Akeneo attribute validation issue
We have Category Validator
PimBundleCatalogBundleEntityCategory:
constraints:
- SymfonyBridgeDoctrineValidatorConstraintsUniqueEntity: code
- PimComponentCatalogValidatorConstraintsImmutable:
properties:
- code
I want ti remove immutable constraint. According to documentation I have to create new validator file, copy-past that code the new file and change what ever I want. But when I do this:
PimBundleCatalogBundleEntityCategory:
constraints:
- SymfonyBridgeDoctrineValidatorConstraintsUniqueEntity: code
or even this
PimBundleCatalogBundleEntityCategory:
constraints:
- SymfonyBridgeDoctrineValidatorConstraintsUniqueEntity: code
- PimComponentCatalogValidatorConstraintsImmutable:
properties:
- dummyField
it merges new validator with the original, so I can't remove immutable constraint from field "code".
I even tried to set empty array as a value of "properties". I tried to set "~" as a value, but it says, that "properties" should be array.
So, how to remove immutability from "code" field?
validation yaml immutability akeneo
asked Jan 18 at 16:03
HevywebHevyweb
2616
Indeed, you can't. It has been designed this way because removing this immutability could break a lot of core features of the PIM, this is why no extension point has been created to remove this check. Why would you remove such a validation / what is your use case?
– grena
2 days ago
add a comment |
This question looks relevant, but it has not answer - Akeneo attribute validation issue
We have Category Validator
PimBundleCatalogBundleEntityCategory:
constraints:
- SymfonyBridgeDoctrineValidatorConstraintsUniqueEntity: code
- PimComponentCatalogValidatorConstraintsImmutable:
properties:
- code
I want ti remove immutable constraint. According to documentation I have to create new validator file, copy-past that code the new file and change what ever I want. But when I do this:
PimBundleCatalogBundleEntityCategory:
constraints:
- SymfonyBridgeDoctrineValidatorConstraintsUniqueEntity: code
or even this
PimBundleCatalogBundleEntityCategory:
constraints:
- SymfonyBridgeDoctrineValidatorConstraintsUniqueEntity: code
- PimComponentCatalogValidatorConstraintsImmutable:
properties:
- dummyField
it merges new validator with the original, so I can't remove immutable constraint from field "code".
I even tried to set empty array as a value of "properties". I tried to set "~" as a value, but it says, that "properties" should be array.
So, how to remove immutability from "code" field?
validation yaml immutability akeneo
asked Jan 18 at 16:03
HevywebHevyweb
2616
This question looks relevant, but it has not answer - Akeneo attribute validation issue
We have Category Validator
PimBundleCatalogBundleEntityCategory:
constraints:
- SymfonyBridgeDoctrineValidatorConstraintsUniqueEntity: code
- PimComponentCatalogValidatorConstraintsImmutable:
properties:
- code
I want ti remove immutable constraint. According to documentation I have to create new validator file, copy-past that code the new file and change what ever I want. But when I do this:
PimBundleCatalogBundleEntityCategory:
constraints:
- SymfonyBridgeDoctrineValidatorConstraintsUniqueEntity: code
or even this
PimBundleCatalogBundleEntityCategory:
constraints:
- SymfonyBridgeDoctrineValidatorConstraintsUniqueEntity: code
- PimComponentCatalogValidatorConstraintsImmutable:
properties:
- dummyField
it merges new validator with the original, so I can't remove immutable constraint from field "code".
I even tried to set empty array as a value of "properties". I tried to set "~" as a value, but it says, that "properties" should be array.
So, how to remove immutability from "code" field?
validation yaml immutability akeneo
validation yaml immutability akeneo
asked Jan 18 at 16:03
HevywebHevyweb
2616
asked Jan 18 at 16:03
HevywebHevyweb
2616
asked Jan 18 at 16:03
HevywebHevyweb
2616
asked Jan 18 at 16:03
HevywebHevyweb
2616
asked Jan 18 at 16:03
HevywebHevyweb
2616
2616
Indeed, you can't. It has been designed this way because removing this immutability could break a lot of core features of the PIM, this is why no extension point has been created to remove this check. Why would you remove such a validation / what is your use case?
– grena
2 days ago
add a comment |
Indeed, you can't. It has been designed this way because removing this immutability could break a lot of core features of the PIM, this is why no extension point has been created to remove this check. Why would you remove such a validation / what is your use case?
– grena
2 days ago
Indeed, you can't. It has been designed this way because removing this immutability could break a lot of core features of the PIM, this is why no extension point has been created to remove this check. Why would you remove such a validation / what is your use case?
– grena
2 days ago
Indeed, you can't. It has been designed this way because removing this immutability could break a lot of core features of the PIM, this is why no extension point has been created to remove this check. Why would you remove such a validation / what is your use case?
– grena
2 days ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54257516%2fakeneo-merge-validators-instead-of-override%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54257516%2fakeneo-merge-validators-instead-of-override%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Indeed, you can't. It has been designed this way because removing this immutability could break a lot of core features of the PIM, this is why no extension point has been created to remove this check. Why would you remove such a validation / what is your use case?
– grena
2 days ago