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

fix: update tsconfig files to match previous config #30856

Merged
merged 6 commits into from
Jan 13, 2025

Conversation

mschile
Copy link
Contributor

@mschile mschile commented Jan 10, 2025

Additional details

#30764 inadvertently removed some necessary config (specifically useDefineForClassFields). This PR adds back the config that was inadvertently removed.

Steps to test

  • Verify when changing specs in open mode, the spec filename is correctly updated.

How has the user experience changed?

Before:
Screenshot 2025-01-10 at 2 15 57 PM

After:
Screenshot 2025-01-10 at 2 21 46 PM

PR Tasks

@alexsch01
Copy link
Contributor

alexsch01 commented Jan 10, 2025

That's strange that a tsconfig change would cause an issue like this
...guess ts-node wasn't happy with it

Copy link

cypress bot commented Jan 10, 2025

cypress    Run #59831

Run Properties:  status check passed Passed #59831  •  git commit 0fd56ba8cc: add test
Project cypress
Branch Review mschile/tsconfig_updates
Run status status check passed Passed #59831
Run duration 17m 42s
Commit git commit 0fd56ba8cc: add test
Committer Matthew Schile
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 4
Tests that did not run due to a developer annotating a test with .skip  Pending 1090
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 26419
View all changes introduced in this branch ↗︎
UI Coverage  45.83%
  Untested elements 190  
  Tested elements 165  
Accessibility  92.55%
  Failed rules  3 critical   8 serious   2 moderate   2 minor
  Failed elements 888  

@cacieprins
Copy link
Contributor

That's strange that a tsconfig change would cause an issue like this ...guess ts-node wasn't happy with it

MobX can't automatically observe fields if this tsconfig option isn't true, unfortunately. This caused some issues with the runner ui. See also: mobxjs/mobx#3216

@mschile mschile merged commit ab2f0c1 into develop Jan 13, 2025
88 of 89 checks passed
@mschile mschile deleted the mschile/tsconfig_updates branch January 13, 2025 15:33
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.

spec filename is not updated when changing specs
5 participants