Skip to content
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

test [M3_8070]: Linting autofixes #11814

Merged

Conversation

dmcintyr-akamai
Copy link
Contributor

@dmcintyr-akamai dmcintyr-akamai commented Mar 10, 2025

Description 📝

Previous PRs under M3_8070 fixed linting errors in the cypress directory. This pr is the result of running npx eslint cypress/e2e/core --fix in the packages/manager directory. This pr applies linting standards to autofix issues in the files. It does not fix all the warnings in the files.

Almost all the changes in this pr are in the packages/manager/cypress/e2e/core. Most of the changes are the result of applying the perfectionist eslint plugin. The most common changes are: reordering of import statements, alphabetical ordering of object attributes, and formatting (indentations, spacing, returns).

Author Checklists

As an Author, to speed up the review process, I considered 🤔

👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support


  • I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

  • All unit tests are passing
  • TypeScript compilation succeeded without errors
  • Code passes all linting rules

@dmcintyr-akamai dmcintyr-akamai changed the title autofix test [M3_8070]: Linting autofixes Mar 12, 2025
@dmcintyr-akamai dmcintyr-akamai marked this pull request as ready for review March 12, 2025 13:21
@dmcintyr-akamai dmcintyr-akamai requested review from a team as code owners March 12, 2025 13:21
@dmcintyr-akamai dmcintyr-akamai requested review from jdamore-linode, abailly-akamai, bill-akamai and cliu-akamai and removed request for a team March 12, 2025 13:21
@dmcintyr-akamai
Copy link
Contributor Author

dmcintyr-akamai commented Mar 12, 2025

The cloud-manager-component-tests reports a failure, but if i re-run the test locally (pnpm run cy:component:run) all the tests succeed. It's unlikely this pr would break the unit tests bc i'm not modifying the code in the src directory.

There is a slight risk that these changes would break some e2e tests by reordering object attribues (some formatting functions are brittle and rely upon the ordering of object attributes, which we have to overrule w/ the "eslint-disable perfectionist/sort-objects" directive) but all the e2e tests are passing.

@linode-gh-bot
Copy link
Collaborator

Cloud Manager UI test results

🔺 1 failing test on test run #4 ↗︎

❌ Failing✅ Passing↪️ Skipped🕐 Duration
1 Failing537 Passing3 Skipped107m 38s

Details

Failing Tests
SpecTest
create-firewall.spec.tscreate firewall » creates a firewall without a linode

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/firewalls/create-firewall.spec.ts"

@dmcintyr-akamai
Copy link
Contributor Author

fwiw cypress/e2e/core/firewalls/create-firewall.spec.ts passes for me locally

@dmcintyr-akamai dmcintyr-akamai merged commit 79f3c6b into linode:develop Mar 12, 2025
25 of 26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants