Addendum to #279
Completely missed this the first time around. When I updated the tests, I believe I was accessing the HereGeocoder constructor directly, thus obscuring this bug.
Sorry that I didn't catch this before a release was pushed.
Perhaps simply passing in extra to the second constructor argument would prevent this mistake in the future?
Addendum to #279 Completely missed this the first time around. When I updated the tests, I believe I was accessing the HereGeocoder constructor directly, thus obscuring this bug.
Sorry that I didn't catch this before a release was pushed.
Perhaps simply passing in
extra
to the second constructor argument would prevent this mistake in the future?