Eyad-Sharkawy commented on PR #6365: URL: https://github.com/apache/fineract/pull/6365#issuecomment-5501057815
Hi team, the api-compatibility-check failed because changing the entity field from a String to an EnumOptionData object is a breaking change, which was requested in FINERACT-817. How does the Fineract team prefer to handle intentional API contract changes? Is there a label I should add to bypass this, or should I preserve the original entity string and add a new field instead? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
