DataModels via Code: edge cases
Description
06 - ACCEPTANCE CRITERIA:
- We should validate if there's clauses that made changes to existing fields. Throw errors
- We should allow the same field to be in different layers of the schema;
Activity
Show:
06 - ACCEPTANCE CRITERIA:
This issue was automatically transitioned to WAITING DEPLOY, as its linked QA regression issue has just reached WAITING DEPLOY status (PR was just merged into master branch in Github).
@Andre Pasold ,
@Geny Isam Hamud Herrera , @Carlos Affonso Wagner , @Andre Pasold , @Moises Jose Soares Filho
This issue was planned to be delivered until 2024-01-22. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-01-22, 2024-01-02
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by andregp,moisesjsf.
Github user moisesjsf has just approved a PR (added as Shard Assignee in this Jira issue).
chore(DM): https://totvslabs.atlassian.net/browse/CAPL-5166#icft=CAPL-5166 JSON schema - handling edge cases
This card has been validated by the QA team.
This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.
This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.
chore(DM): https://totvslabs.atlassian.net/browse/CAPL-5166#icft=CAPL-5166 JSON schema - handling edge cases
@Andre Pasold ,
@Pedro Buzzi , @Carlos Affonso Wagner ,
This issue was planned to be delivered until 2024-01-01. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-01-01
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.