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

Updated README and CONTRIBUTING instructions #75

Merged
merged 1 commit into from
Jul 23, 2024
Merged

Updated README and CONTRIBUTING instructions #75

merged 1 commit into from
Jul 23, 2024

Conversation

cgalvan
Copy link
Collaborator

@cgalvan cgalvan commented Jul 23, 2024

Description

Updated the documentation with instructions on how to use the adapter.

  • Added instructions to README on how to create the necessary map/places/routes resources and create an API key with access to them
  • Added guide to the README for how to import the adapter based on which Google Maps import method is being used
  • Moved the development setup/examples instructions to the CONTRIBUTING file

@cgalvan cgalvan requested a review from a team as a code owner July 23, 2024 19:39
@cgalvan cgalvan merged commit 9434846 into aws-geospatial:main Jul 23, 2024
1 check passed
@cgalvan cgalvan deleted the UpdatedREADME branch July 23, 2024 20:00
git clone https://github.com/<YOUR_GITHUB_USERNAME>/amazon-location-migration-adapter
cd amazon-location-migration-adapter
git remote add upstream https://github.com/aws-geospatial/amazon-location-migration-adapter.git
git remote set-url --push upstream THESE_ARENT_THE_DROIDS_WERE_LOOKING_FOR
Copy link
Contributor

Choose a reason for hiding this comment

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

The clear instructions are super helpful


Each example has an `index.html` and a `google.html` page, of which the only difference between them is that the `index.html` imports our migration adapter.
The examples also have an `example.js` script that holds the client logic for the example. This client logic is shared between both `index` and `google` example pages
in order to showcase that the client logic can invoke the same `google.maps` APIs, but will be re-routed by the migration adapter for any APIs that the migration adapter supports.
Copy link
Contributor

Choose a reason for hiding this comment

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

Explanation very much needed for new users

Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks for adding!

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.

4 participants