Update exchange-rates.md #31566
Merged
Update exchange-rates.md #31566
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
|
octavia-squidington-iii
added
area/documentation
marcosmarxm
approved these changes
Oct 18, 2023
|
/approve-and-merge reason="only doc changes" |
|
A crack team of mammals has made a decision. |
octavia-approvington
approved these changes
Oct 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update links in documentation to API layer docs
What
Describe what the change is solving
It helps to add screenshots if it affects the frontend.
Links in exchange rates documentation point to legacy API endpoint documentation, this has been migrated to API layer in PR 15884. I've just updated the documentation to include the new API docs
How
Describe the solution
Edited some links in markdown files
Recommended reading order
🚨 User Impact 🚨
Are there any breaking changes? What is the end result perceived by the user?
No user impact, except improved ease when setting up connection
For connector PRs, use this section to explain which type of semantic versioning bump occurs as a result of the changes. Refer to our Semantic Versioning for Connectors guidelines for more information. Breaking changes to connectors must be documented by an Airbyte engineer (PR author, or reviewer for community PRs) by using the Breaking Change Release Playbook.
If there are breaking changes, please merge this PR with the 🚨🚨 emoji so changelog authors can further highlight this if needed.
No breaking changes, unsure if even a minor version bump is necessary for just a documentation change
Pre-merge Actions
Expand the relevant checklist and delete the others.
Updating a connector
Community member or Airbyter
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.