Fix header navigation bar and playwright test

[Xpirix]

This is a proposed fix for the header navigation bar and the playwright e2e test workflow. I've also changed Product to Project in the test fixture for the header as they have been changed in the header navigation bar.

A preview of the header is available at: https://qgis.github.io/qgis-uni-navigation/

Summary by CodeRabbit

• Chores
  • Updated the URL for the navigation web component.
• Tests
  • Modified test scripts to align with updated link references in the app's header and sidebar.

[coderabbitai]

Walkthrough

The recent updates focus on renaming elements from productLink to projectLink across various test scripts and fixtures in a Playwright CI test suite. Additionally, a URL in the configuration file for a web component was changed to reflect a new hosting location.

Changes

File Path	Change Summary
config.toml	Updated the URL for the navigation web component.
.../01-home-page.spec.ts .../02-download-page.spec.ts .../03-product-page.spec.ts	Updated tests to interact with projectLink instead of productLink.
.../fixtures/header.ts .../fixtures/sidebar.ts	Renamed productLink to projectLink and updated locators.

Poem

🐇💻 CodeRabbit's Ode to Change 🌟
"From product to project, a link leaps anew,
Guiding through pages as fresh URLs brew.
Clicks in the tests now seek different spots,
In headers and sidebars, the changes plot.
Hop along, dear code, in your refined dance,
Every update a step, in progress's prance."

---

Recent Review Details

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between a330301 and 747bb6c.

Files selected for processing (6)

• config.toml (1 hunks)
• playwright/ci-test/tests/01-home-page.spec.ts (2 hunks)
• playwright/ci-test/tests/02-download-page.spec.ts (1 hunks)
• playwright/ci-test/tests/03-product-page.spec.ts (1 hunks)
• playwright/ci-test/tests/fixtures/header.ts (2 hunks)
• playwright/ci-test/tests/fixtures/sidebar.ts (2 hunks)

Additional comments not posted (7)

playwright/ci-test/tests/02-download-page.spec.ts (1)

36-36: Updated the sidebar link interaction from productLink to projectLink correctly.

playwright/ci-test/tests/03-product-page.spec.ts (1)

30-30: Updated the sidebar link interaction from productLink to projectLink correctly.

playwright/ci-test/tests/fixtures/header.ts (2)

7-7: Renamed productLink to projectLink correctly.

---

36-38: Updated the method to obtain the projectLink locator to use getByText with an exact match correctly.

playwright/ci-test/tests/fixtures/sidebar.ts (1)

5-5: Renamed productLink to projectLink correctly.

playwright/ci-test/tests/01-home-page.spec.ts (1)

35-35: Updated the test to interact with the projectLink instead of the productLink in the Header section correctly.

config.toml (1)

85-85: Updated the URL for the navigation web component correctly.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.