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

Upgrade pelias-parser to v2.0.0 #1565

Merged
merged 1 commit into from
Oct 11, 2021
Merged

Upgrade pelias-parser to v2.0.0 #1565

merged 1 commit into from
Oct 11, 2021

Conversation

missinglink
Copy link
Member

@missinglink missinglink commented Oct 5, 2021

As discussed in #1550, this PR takes us off a branch of pelias-parser and gets us back on the latest published version.

Noteworthy changes from pelias/parser being brought in:

Original commit to pin pelias-parser to a branch: 4061a2f

closes #1550

@orangejulius
Copy link
Member

Excellent. To be honest I think we can save everyone some trouble and not mark this as a breaking change. Unit number parsing has been removed in the API for some time, and even before then I'm pretty sure the queries in API didn't take advantage of any unit number that was found when parsing.

@orangejulius
Copy link
Member

What testing do you think we should do before releasing this? The unit number removal is, of course, well tested at this point, but I'd be interested to see the impact of other changes (hopefully there are improvements!)

Changes in pelias/parser being brought in:
- pelias/parser@72d6463
- pelias/parser@90481c5
- pelias/parser@94eae1b
- pelias/parser@e92f96c
- pelias/parser@a1af69b

Original commit to pin pelias-parser to a branch:
4061a2f
@orangejulius orangejulius changed the title feat(parser): upgrade pelias-parser dependency Upgrade pelias-parser to v2.0.0 Oct 11, 2021
@orangejulius
Copy link
Member

We've tested this out extensively across all our test suites and there are no major regressions. (We've catalogued the two small ones we found in pelias/parser#151 and pelias/parser#152).

There are probably quite a few improvements to parsing in the Netherlands especially, I think we'll be following up more closely on that.

@orangejulius orangejulius merged commit 04f65c3 into master Oct 11, 2021
@orangejulius orangejulius deleted the parser_dep_upgrade branch October 11, 2021 22:05
orangejulius added a commit that referenced this pull request Nov 29, 2021
Historically we've kept most Pelias NPM dependencies on carat versions,
but because the Pelias Parser can cause changes in acceptance-test
results for any change (minor or even bug fix), we've kept it pinned to
a specific version so we can explicitly upgrade.

Recently, we were on a [hotfix
branch](#1531) of the parser, but
while switching back to using a version specification, we switched to
[using a carat
range](#1565).

While manually bumping the version on a frequent basis is a bit
annoying, it helps avoid any chance that unexpected or untested parser
changes will find their way into the API releases, so this change brings
us back to a pin of the current latest version of the Pelias Parser.
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.

upgrade pelias/parser
2 participants