-
Notifications
You must be signed in to change notification settings - Fork 980
feat: report console issues in list_console_messages #505
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
Conversation
|
There are conflicts with the main branch. Could you please rebase? |
9665ceb to
0a00958
Compare
OrKoN
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! let's also add tests to make sure everything is working end-to-end and please address the lint and formatting issues.
f964f7b to
7fef676
Compare
7fef676 to
0aa6659
Compare
I think we still need a e2e test similar to tests in tests/McpContext.test.ts in which we use Puppeteer to actually navigate to a page that has an issue. We can pick an issue that is easy to trigger via page.setContent(). |
Co-authored-by: Alex Rudenko <OrKoN@users.noreply.github.com>
5480ba1 to
51e1d9b
Compare
|
LGTM thanks! |
Now that all PRs by @nattallius have landed, this PR removes the feature flag introduced in #575 and makes issues available by default. - list_console_messages has a new message type called `issue` to filter for DevTools issues - get_console_message returns details for the issues. DevTools issues help to identify and fix problems on web pages. See https://developer.chrome.com/docs/devtools/issues for more details. PRs contributing this feature: - #505 - #594 - #594
BEGIN_COMMIT_OVERRIDE
chore: report console issues in list_console_messages
END_COMMIT_OVERRIDE