Fix URL path in documentation link to ensure correct format #1536
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.
Checklist
Issue/User story
The pull request addresses an issue where the documentation link on the landing page generates a URL with an incorrect path, specifically introducing double slashes (
//
) after the version number, leading to inconsistent URL formatting.Steps to Reproduce
//
after the version number.Existing issues
Design of the fix
The fix involved removing the additional slash from the
href
attribute in the anchor tag for the documentation link. This approach was chosen because it directly addresses the root cause of the issue - an extra slash introduced in the URL path, ensuring that URLs are generated correctly without manual intervention or further processing.Validation of the fix
Manual testing was conducted to confirm that the URL is now correctly formatted without double slashes.
Automated Tests
No new automated tests were added as the fix is straightforward and does not introduce new functionality. Existing tests ensure that the documentation links are accessible and lead to the correct pages.
What documentation has been provided for this pull request
N/A - The change does not introduce new functionality or concepts that require additional documentation beyond the code change itself.