Skip to content

Conversation

@jdschleicher
Copy link
Owner

Motivation and Context

[Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here]

What does this PR do?

[Provide a clear and concise description of the changes in this PR]

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Other (please describe):

How Has This Been Tested?

  • Tested on Windows
  • Tested on macOS
  • Tested on Linux
  • Added new unit tests
  • Updated existing tests

Test Details

[Describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration]

Checklist

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

Additional Notes

[Add any other context, screenshots, or relevant information about the PR here]

Reviewers

@mention-team-members-or-specific-reviewers

jdschleicher and others added 30 commits February 25, 2025 09:16
…ield doesn't include a controlling value, we want to capture whether that record type markup has the field being processed referenced to begin with in its valueSet markup
…bject and api name found in mappings correctly
@jdschleicher jdschleicher deleted the bugtesting/1.3.0 branch April 29, 2025 11:48
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.

1 participant