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(Swift): Addressing some gaps in Geo Gen2 doc pages #7573
Conversation
src/pages/[platform]/build-a-backend/add-aws-services/geo/set-up-geo/index.mdx
Outdated
Show resolved
Hide resolved
Make sure to generate the `amplify_outputs.json` file by running the following command: | ||
|
||
```bash title="Terminal" showLineNumbers={false} | ||
npx ampx sandbox | ||
``` |
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.
should this be moved outside the swift block? I think we should keep the prose relatively the same across platforms (with a few exceptions) for maintainability and a concise UX
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.
We could explore doing that in the future as a docs clean up, but right now each platform is doing its own thing
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.
platform-specific callouts were (mostly) cleaned up when content was ported into this new structure. swift has the callout to move the file into the project, which is fine, but prose should be relatively the same
…up-geo/index.mdx Co-authored-by: josef <josef.aidt@gmail.com>
Description of changes:
This PR addresses the following issues within the Swift Gen2 documentation for Geo:
Set up Amplify Geo
amplify_outputs.json
file to the project.Work with maps
Configure location search
aws_region
to the backend code snippet.Work with location search
Related GitHub issue #, if available:
Instructions
If this PR should not be merged upon approval for any reason, please submit as a DRAFT
Which product(s) are affected by this PR (if applicable)?
Which platform(s) are affected by this PR (if applicable)?
Please add the product(s)/platform(s) affected to the PR title
Checks
Does this PR conform to the styleguide?
Does this PR include filetypes other than markdown or images? Please add or update unit tests accordingly.
Are any files being deleted with this PR? If so, have the needed redirects been created?
Are all links in MDX files using the MDX link syntax rather than HTML link syntax?
ref: MDX:
[link](https://docs.amplify.aws/)
HTML:
<a href="https://docs.amplify.aws/">link</a>
When this PR is ready to merge, please check the box below
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.