Skip to content

TypeScript: strict parameter type for location #5574

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

Merged
merged 3 commits into from
Dec 19, 2019

Conversation

OliverJAsh
Copy link
Contributor

@OliverJAsh OliverJAsh commented Nov 1, 2019

  • Closes

User facing changelog

The type definitions for cy.location() have been improved.

Additional details

cy.location('path') // type error
cy.location('pathname') // ✅

How has the user experience changed?

PR Tasks

Sorry, something went wrong.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
@cypress-bot
Copy link
Contributor

cypress-bot bot commented Nov 1, 2019

Thanks for the contribution! Below are some guidelines Cypress uses when doing PR reviews.

  • Please write [WIP] in the title of your Pull Request if your PR is not ready for review - someone will review your PR as soon as the [WIP] is removed.
  • Please familiarize yourself with the PR Review Checklist and feel free to make updates on your PR based on these guidelines.

PR Review Checklist

If any of the following requirements can't be met, leave a comment in the review selecting 'Request changes', otherwise 'Approve'.

User Experience

  • The feature/bugfix is self-documenting from within the product.
  • The change provides the end user with a way to fix their problem (no dead ends).

Functionality

  • The code works and performs its intended function with the correct logic.
  • Performance has been factored in (for example, the code cleans up after itself to not cause memory leaks).
  • The code guards against edge cases and invalid input and has tests to cover it.

Maintainability

  • The code is readable (too many nested 'if's are a bad sign).
  • Names used for variables, methods, etc, clearly describe their function.
  • The code is easy to understood and there are relevant comments explaining.
  • New algorithms are documented in the code with link(s) to external docs (flowcharts, w3c, chrome, firefox).
  • There are comments containing link(s) to the addressed issue (in tests and code).

Quality

  • The change does not reimplement code.
  • There's not a module from the ecosystem that should be used instead.
  • There is no redundant or duplicate code.
  • There are no irrelevant comments left in the code.
  • Tests are testing the code’s intended functionality in the best way possible.

Internal

  • The original issue has been tagged with a release in ZenHub.

@CLAassistant
Copy link

CLAassistant commented Nov 1, 2019

CLA assistant check
All committers have signed the CLA.

@jennifer-shehane jennifer-shehane requested a review from a team December 19, 2019 08:07

Verified

This commit was signed with the committer’s verified signature. The key has expired.
flotwig Zach Bloomquist

Verified

This commit was signed with the committer’s verified signature. The key has expired.
flotwig Zach Bloomquist
Copy link
Contributor

@flotwig flotwig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR!

I changed it to use keyof Location instead of keyof Window['location'], which is different from what cy.location resolves with when no arguments are passed, updated the return type to use the expected type from Location, and added some tests.

@flotwig flotwig merged commit 78d0536 into cypress-io:develop Dec 19, 2019
@OliverJAsh
Copy link
Contributor Author

Thank you! Can you ping me when this is released?

@bahmutov
Copy link
Contributor

@OliverJAsh our release bot will comment on the issue whenever it gets released, so you will get an email

@cypress-bot
Copy link
Contributor

cypress-bot bot commented Dec 26, 2019

Released in 3.8.1.

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.

None yet

4 participants