Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DXCDT-380: shouldFieldBePreserved function #738

Merged
merged 2 commits into from
Feb 10, 2023

Conversation

willvedd
Copy link
Contributor

🔧 Changes

The first part of many to implement a fix for #328. At the most basic level, we need to identify which fields to preserve before can actually preserve them.

This function doesn't serve much function in its current form, but it will be used by higher-order functions to compose the keyword preservation functionality.

This PR starts to lay the foundation for the keyword preservation code in both the keywordPreservation.ts file as well as the accompanying test file.

📚 References

Related Issues:

🔬 Testing

Many unit tests included to cover a wide-range of situations.

📝 Checklist

  • All new/changed/fixed functionality is covered by tests (or N/A)
  • I have added documentation for all new/changed functionality (or N/A)

@willvedd willvedd requested a review from a team as a code owner February 10, 2023 12:27
@willvedd willvedd enabled auto-merge (squash) February 10, 2023 12:28
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.

2 participants