-
Notifications
You must be signed in to change notification settings - Fork 0
Fix buttons url #1
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
Conversation
- Update link to Local Setup Guide in mobile-client/index.mdx - Update relative links in web-dashboard/deployment.mdx, web-dashboard/local-setup.mdx, and web-dashboard/web-dashboard.mdx
- Update hero action link from '/getting-started/' to '/docs/getting-started/' - Update LinkButton href from '/getting-started/' to '/docs/getting-started/'
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.
Summary of Changes
Hello @fulleni, I'm Gemini Code Assist1 ! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request addresses issues with internal navigation within the documentation by correcting various broken or incorrect links. The changes ensure that users can seamlessly navigate through the setup, deployment, and general information guides, improving the overall usability of the documentation.
Highlights
- Documentation Link Corrections: I've updated several internal links within the documentation to ensure correct navigation. This includes prepending
/docsto some paths and converting absolute paths to relative paths where appropriate, resolving issues with broken or incorrect URLs.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
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.
Code Review
This pull request aims to fix URLs in the documentation. While some links are correctly updated, several changes introduce incorrect relative paths, which will likely result in broken links. I've provided suggestions to correct these paths to ensure the documentation remains navigable.
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.
The updated relative link appears to be incorrect. From src/content/docs/mobile-client/index.mdx, the link ./mobile-client/local-setup would resolve to .../mobile-client/mobile-client/local-setup, which is not the intended path. Since local-setup.mdx is in the same directory, the correct relative link should be ./local-setup.
- **[Local Setup Guide](./local-setup)**
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.
This change from an absolute path to a relative path seems to have introduced an incorrect link. The file is located at src/content/docs/web-dashboard/deployment.mdx, and the target is src/content/docs/api-server/deployment.mdx. The relative path ./api-server/deployment/ would resolve to .../web-dashboard/api-server/deployment/, which is incorrect. The correct relative path should go up one level.
Ensure that the `baseUrl` for the `production` environment in `lib/app/config/app_config.dart` points to the correct URL of your deployed [API Server](../api-server/deployment/).
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.
The updated relative link appears to be incorrect. This file is at src/content/docs/web-dashboard/local-setup.mdx. The link ./getting-started/local-setup-api would resolve to .../web-dashboard/getting-started/local-setup-api, which is likely not the intended file. Assuming you are linking to the API server's local setup guide (src/content/docs/api-server/local-setup.mdx), the correct relative path would be ../api-server/local-setup/.
For the `development` environment, you must have the [API Server running locally](../api-server/local-setup/) first.
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.
This change from an absolute path to a relative path seems to have introduced an incorrect link. The file is located at src/content/docs/web-dashboard/web-dashboard.mdx, and the target is likely src/content/docs/api-server/deployment.mdx. The relative path ./deployment/api-server/ would resolve to .../web-dashboard/deployment/api-server/, which is incorrect. The correct relative path should go up one level to ../ and then into api-server/deployment/.
Ensure that the `baseUrl` for the `production` environment in `lib/app/config/app_config.dart` points to the correct URL of your deployed [API Server](../api-server/deployment/).
No description provided.