Open MikeAlhayek opened 2 years ago
Looks legit. Maybe if you debug it you can find where it's taking the description from and where the issue is?
@CrestApps It's by design
If named BagPart on content item sets empty description then it falls back to BagPart description. Set Description on BagPart as Empty.
I am not sure if inheriting the description from BagPart
is user friendly. IMO, since we attached a named Bag here, the description in the named part should be honored regardless.
@CrestApps hm may true.
May be not - having .WithDescription("")
is equivalent of not having that statement at all.
Ideally in OOPs not overriding property means it's takes from base- Here In this case - null or empty string in your content type named part falls back to content part desc.
If you don't want to have anything you can try and add a " " whitespace in the description too. Have not tried but that may work and remove the inherited description.
-: If you prefere migration :- You can remove desc from base part ( i.e. BagPart) using migration from any module that has dependency on "Flow" with following code
_contentDefinitionManager.AlterPartDefinition("BagPart", builder => builder
.WithDescription(""));
Describe the bug
I attached two named BagPart like the following
But I can't seems to clear out the default description of the attached part. Event when I removed the description from the UI, I'll keep coming back as "Provides a collection behavior for your content item where you can place other content items."
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I should not have to provide a description if I chose not to.
Screenshots
If applicable, add screenshots to help explain your problem.