Remove cutoff_frequency, deprecated in es7.3.0, forbidden in es8 #1657
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.
Here's the reason for this change 🚀
In pursuit of eventually supporting es8, I've dropped some es6 only behavior in pelias/query#134.
It's a draft because it depends on pelias/query#134 being released first.
Here's what actually got changed 👏
cutoff_frequency
.Here's how others can test the changes 👀
Other than
npm test
, I've run the north-america tests.Note: The north-america tests aren't all passing, but the ones that are failing are exactly the same as when I run from current master. I'm assuming (🤞) that the failures reflect changes in the input data since the tests were updated, as hypothesized over here.
north-america integration test output before
north-america test output after