Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

test: verify that there are no errors on the website#6365

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged

Conversation

Jefiozie
Copy link
Contributor

@JefiozieJefiozie commentedJan 22, 2023
edited
Loading

PR Checklist

Overview

I've made some small changes to test if there are any errors on the website by listening to theconsole. Added a second test with the opposite for verification. Happy to improve some more if needed.

@JoshuaKGoldberg I've made the choice not to search for a library as the tests are pretty simple and have no "magic" from the library.

Update: hmm I'm not sure what I'm doing wrong here. On my machine I don't see any issues. Am I'm missing a step if I just run the playwrih test with NX?

@nx-cloud
Copy link

nx-cloudbot commentedJan 22, 2023
edited
Loading

☁️ Nx Cloud Report

CI is running/has finished running commands for commit5222df7. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch


✅ Successfully ran 25 targets

Sent with 💌 fromNxCloud.

@typescript-eslint
Copy link
Contributor

Thanks for the PR,@Jefiozie!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!


🙏Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently onhttps://opencollective.com/typescript-eslint.

@netlify
Copy link

netlifybot commentedJan 22, 2023
edited
Loading

Deploy Preview fortypescript-eslint ready!

NameLink
🔨 Latest commit5222df7
🔍 Latest deploy loghttps://app.netlify.com/sites/typescript-eslint/deploys/63d0e8f82a0162000834d3bc
😎 Deploy Previewhttps://deploy-preview-6365--typescript-eslint.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to yourNetlify site settings.

Copy link
Member

@JoshuaKGoldbergJoshuaKGoldberg left a comment

Choose a reason for hiding this comment

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

A good start! Hope this helps with the debugging, but let me know if not. 🙂

@Jefiozie
Copy link
ContributorAuthor

Jefiozie commentedJan 24, 2023
edited by JoshuaKGoldberg
Loading

hi@JoshuaKGoldberg, I've made the requested changes, thanks for your feedback. I'm not sure why the test on CI keeps failing. Running the website project locally withnpx nx test website doesn't return the error that is descibribed in the CI test.
Do you build the website in a different way then the defaultnpx nx build website?

@JoshuaKGoldberg
Copy link
Member

Ooh I do get that error locally fromnpx nx website start (also when running it as aliased underyarn start)!

Screenshot of Chrome devtools error: 'react-dom.development.js?3c4a:86 Warning: ReactDOM.render is no longer supported in React 18. Use createRoot instead. Until you switch to the new API, your app will behave as if it's running React 17. Learn more: https://reactjs.org/link/switch-to-createroot'

So this PR will have to account for that message. At least untilfacebook/docusaurus#7264 comes in.

Copy link
Member

@JoshuaKGoldbergJoshuaKGoldberg left a comment

Choose a reason for hiding this comment

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

Requesting changes to get a passing build - but hey, nice to know the new test is working! 😄

@JoshuaKGoldbergJoshuaKGoldberg added the awaiting responseIssues waiting for a reply from the OP or another party labelJan 24, 2023
@Jefiozie
Copy link
ContributorAuthor

So now the test are running for the website check. I'm not sure why the other tests are failing. Is this a known issue in the workflows? If I need to change anything just let me know.

Thanks for the feedback@JoshuaKGoldberg

@JoshuaKGoldberg
Copy link
Member

Huh, I hadn't seen those failures before. Must be a transient issue in GitHub Actions...

Copy link
Member

@JoshuaKGoldbergJoshuaKGoldberg 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 iterating on this@Jefiozie! Great stuff. 😄

@JoshuaKGoldbergJoshuaKGoldbergenabled auto-merge (squash)January 25, 2023 17:30
@JoshuaKGoldbergJoshuaKGoldberg merged commit033e87c intotypescript-eslint:mainJan 25, 2023
@JefiozieJefiozie deleted the addErrorCheck branchJanuary 25, 2023 17:57
@github-actionsgithub-actionsbot locked asresolvedand limited conversation to collaboratorsFeb 2, 2023
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@JoshuaKGoldbergJoshuaKGoldbergJoshuaKGoldberg approved these changes

Assignees
No one assigned
Labels
awaiting responseIssues waiting for a reply from the OP or another party
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Repo: End-to-end test that no console errors are logged on the homepage
2 participants
@Jefiozie@JoshuaKGoldberg

[8]ページ先頭

©2009-2025 Movatter.jp