Skip to content

Fixes ISSUE-45260: Remove shouldAddDeprecation and deprecation method arg

Cristian Berner requested to merge cristian.berner/backoffice-api:fix/45260-depr into master

Related to MR: openbravo/product/openbravo!161 (merged)

Entities and properties will be deprecated by default if marked as deprecated instead of having an optional argument to activate the deprecation. This means those shouldAddDeprecation method is not needed anymore and an argument to differentiate between adding or removing deprecation is also not needed.

GenerateEntitiesTask.shouldAddDeprecation method has been removed ModelProvider.addHelpAndDeprecationToModel method has no argument now (previously it had a boolean)

API Changes

API Change Type Status Comment
GenerateEntitiesTask.shouldAddDeprecation() Method Removed Not needed anymore, will add deprecation by default
ModelProvider.addHelpAndDeprecationToModel(boolean) Method Boolean argument removed The boolean argument is not needed anymore, as deprecation is added by default

Task

Edited by Cristian Berner

Merge request reports