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
feat: autosuggest place id support #173
feat: autosuggest place id support #173
Conversation
Codecov Report
@@ Coverage Diff @@
## main #173 +/- ##
==========================================
+ Coverage 42.94% 43.67% +0.72%
==========================================
Files 16 16
Lines 1248 1264 +16
Branches 169 170 +1
==========================================
+ Hits 536 552 +16
Misses 712 712
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you tried testing this change with the new geocoder changes? Otherwise LGTM
Also I believe we may need to preface this PR title with |
🎉 This PR is included in version 2.1.0-unstable.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
* feat: add Geocoder APIs with test data - getSuggestions, searchByPlaceId * chore: update getSuggestions and searchByPlaceId APIs with unit tests and proper return types * fix: fix unit test and check for undefined return value * chore: use newer version of maplibre-gl-geocoder * chore: use latest @aws-amplify/geo * chore: use latest @aws-amplify/geo
Description of changes
Add getSuggestions and searchByPlaceId APIs with unit tests
Issue #, if available
Description of how you validated changes
Manual testing with test data on UI component and unit tests.
Checklist
yarn test
passes