Oleg Zhuk

@alynabriscoe Thanks for idea As workaround, we added options to find all links in catalogue module 3.202 1. Go to product (category) 2. Open properties 3. You should be able...

Add ReleaseNotes Link into manifest Provide ability to click and open ReleaseNotes in new tab

Same problem with this file: swagger-markdown -i VirtoCommerce.DynamicAssociationsModule.yaml RangeError: Maximum call stack size exceeded at Pointer.resolve (C:\Users\OlegZhuk\AppData\Roaming\npm\node_modules\swagger-markdown\node_modules\@apidevtools\json-schema-ref-parser\lib\pointer.js:76:24) [VirtoCommerce.DynamicAssociationsModule.yaml.txt](https://github.com/syroegkin/swagger-markdown/files/8804011/VirtoCommerce.DynamicAssociationsModule.yaml.txt)

Added fix into https://github.com/VirtoCommerce/vc-platform/pull/2615

To implement this functionality: 1. Develop a custom module tailored to your specific requirements. 1. Utilize the BlobCreatedEvent subscription mechanism. Added in https://github.com/VirtoCommerce/vc-module-assets/pull/19. 1. Enhance the implementation by incorporating validation...

@alynabriscoe @Dan-BV I think, it's correct behaviour. By default. if you update/delete the value in the dictionary for a given property, that change is not propagated to the items with...

### Expected behavior 1. Create a new category [Test] and click save 2. Create a new category with [Test], click save, Display warning "folder name already exists", create Yes or...

@qq550723504 VirtoCommerce supports multiple categories with same name, it provides ability to display different products for different customers and etc. I offer to add custom SQL constrain on CatalogId, ParentCategoryId,...

I used workaround ```````` private readonly Func _catalogRepositoryFactory; using (var catalogRepository = _catalogRepositoryFactory()) { return catalogRepository.Categories.Where(c => c.CatalogId == catalogId && c.Code == categoryCode).Select(c => c.Id).FirstOrDefault(); } ````````

@j-mok thank you for the update, we will check the code, if all is ok, we will merge, if not I will plan to applying the breaking changes on end...