There is a scenario where the API First pattern is used in a Gradle project in which multiple developers are working. The project contains several YAML fragments with paths and schemas, and each developer works on some of these fragments.
At times, a schema with the same name but different attributes is created in different fragments by different developers.
To make the developer's work easier, it would be helpful if, instead of the merge ignoring the schema duplication, an error was raised during the execution of the merge task, and this option could be configured.
Hi,
There is a scenario where the API First pattern is used in a Gradle project in which multiple developers are working. The project contains several YAML fragments with paths and schemas, and each developer works on some of these fragments.
At times, a schema with the same name but different attributes is created in different fragments by different developers.
To make the developer's work easier, it would be helpful if, instead of the merge ignoring the schema duplication, an error was raised during the execution of the merge task, and this option could be configured.