Skip to content

Fix #304 - #363

Merged
antoineatstariongroup merged 2 commits into
developmentfrom
304-feature-textual-notation-validation-18-use-case-use-case
Aug 31, 2026
Merged

Fix #304#363
antoineatstariongroup merged 2 commits into
developmentfrom
304-feature-textual-notation-validation-18-use-case-use-case

Conversation

@antoineatstariongroup

Copy link
Copy Markdown
Collaborator

Prerequisites

  • I have written a descriptive pull-request title
  • I have verified that there are no overlapping pull-requests open
  • I have verified that I am following the SysML2.NET code style guidelines
  • I have provided test coverage for my change (where applicable)

Description

Fix #304

Validation of 18-Use Case

@antoineatstariongroup antoineatstariongroup linked an issue Aug 31, 2026 that may be closed by this pull request
6 tasks
@sonarqubecloud

Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
57.1% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

@antoineatstariongroup
antoineatstariongroup merged commit eed5ee5 into development Aug 31, 2026
7 of 8 checks passed
@antoineatstariongroup
antoineatstariongroup deleted the 304-feature-textual-notation-validation-18-use-case-use-case branch August 31, 2026 13:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: Textual Notation validation — 18-Use Case (Use Case)

1 participant