Skip to content

TIG use case#1556

Merged
SFJohnson24 merged 22 commits intomainfrom
tig_custom
Feb 5, 2026
Merged

TIG use case#1556
SFJohnson24 merged 22 commits intomainfrom
tig_custom

Conversation

@SFJohnson24
Copy link
Collaborator

@SFJohnson24 SFJohnson24 commented Jan 22, 2026

this PR along with the editor PR adds -use-case to scope rules for TIG. This allows the custom domains to be ruled as in scope and have the rule fire for them.
This resolves the issue with the custom domains running for TIG0514 from the original ticket.

Note: the YP class is out of scope so that rule will not fire but the two X- domains will

@SFJohnson24 SFJohnson24 marked this pull request as ready for review January 23, 2026 17:42
@SFJohnson24 SFJohnson24 self-assigned this Jan 23, 2026
}

def get_conformance_details_data(
def get_conformance_details_data( # noqa
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please mention the reason for skipping the lint check here now?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ignoring complexity check to keep the conformance detail data as one function--it is not complex, it just needs to fill in each field of the conformance details

)
@click.pass_context
def validate(
def validate( # noqa
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as above.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as above--I wanted to keep validate as a single functional unit

Copy link
Collaborator

@RamilCDISC RamilCDISC left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR updates the use case processing for TIG. Instead of hardcoded use case now comes from the dataset. The PR was validated by:

  1. Reviewing the PR for any unwanted code or comments.
  2. Reviewing the PR logic in accordance with AC.
  3. Ensuring all unit and regression testing pass.
  4. Ensuring relevant testing is updated.
  5. Ensuring relevant documentation is updated.
  6. Ensuring execution for editor and cli is not affected.
  7. Running manual validation using a rule in local editor.
  8. Running manual validation using a rule in CLI.
  9. Ensuring case when use case matching to rule is mentioned in dataset.
  10. Case when use case in dataset is different than the rule.
  11. Case when use case is missing.
  12. Case when there are multiple use cases in dataset.

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.

Operation: domain_is_custom is currently not working for TIG standard.

3 participants