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

Fix/geo location services config #13303

Merged

Conversation

ashwinkumar6
Copy link
Contributor

@ashwinkumar6 ashwinkumar6 commented Apr 27, 2024

Description of changes

Original PR: fix: (Geo) Kebab case to Camel case config props

Description of how you validated changes

Tested changes on sample app

Checklist

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@ashwinkumar6 ashwinkumar6 requested review from a team as code owners April 27, 2024 18:21
@ashwinkumar6 ashwinkumar6 force-pushed the fix/geo-location-services-config branch from cfef59c to 27fb817 Compare April 27, 2024 18:26
ashika112
ashika112 previously approved these changes Apr 27, 2024
ashika112
ashika112 previously approved these changes Apr 27, 2024
AllanZhengYP
AllanZhengYP previously approved these changes Apr 27, 2024
ashika112
ashika112 previously approved these changes Apr 27, 2024
Copy link
Contributor

@calebpollman calebpollman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for taking care of this! Do think the updates should be fine, but with the relevant code of this PR mirroring #12921, the concerns I had there have not changed:

  • This code has been in production for almost 6 months, what assurances do we have that this change won't cause any impact on existing usage? I'm sure that we've tested for regressions already, but can you please explain what exactly has been done testing and what safeguards are in place to ensure a lack of regression?

  • Regarding the actual root cause, need to see it addressed along with unit tests. A small targeted unit test of the Geo configuration would have prevented the issue initially, and can go a long way in catching potential regressions in the future

packages/core/src/parseAWSExports.ts Outdated Show resolved Hide resolved
@esalacupnamde
Copy link

@ashwinkumar6 great job on this!!!

@ghost
Copy link

ghost commented Apr 27, 2024

WoW....Really Appreciate doing it..

@@ -335,7 +335,7 @@
"name": "[API] generateClient (AppSync)",
"path": "./dist/esm/api/index.mjs",
"import": "{ generateClient }",
"limit": "39.99 kB"
"limit": "40.09 kB"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfectoooo

@@ -151,7 +151,7 @@ export class AmazonLocationServiceProvider implements GeoProvider {
*/
let locationServiceInput: SearchPlaceIndexForTextCommandInput = {
Text: text,
IndexName: this._config.search_indices.default,
IndexName: this._config.searchIndices.default,
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GG : )

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GG : )

Copy link
Contributor

@AllanZhengYP AllanZhengYP left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍Always a nice change to eliminate every code path that could go wrong. Approve from JS side. I defer to @calebpollman to confirm potential UI change.

Copy link
Contributor

@calebpollman calebpollman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚢

@ashika112 ashika112 merged commit fa02396 into aws-amplify:main Apr 28, 2024
30 checks passed
ghost

This comment was marked as abuse.

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.

None yet

7 participants