Adding shouldFieldBePreserved
function
#736
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🔧 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