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

Fixed: Mojo::DOM doesn't recognize end of comment (when it should) #2… #2080

Closed
wants to merge 3 commits into from

Conversation

poti1
Copy link

@poti1 poti1 commented Jun 24, 2023

…030.

#2030

t/mojo/dom.t Outdated Show resolved Hide resolved
lib/Mojo/DOM/HTML.pm Outdated Show resolved Hide resolved
lib/Mojo/DOM/HTML.pm Outdated Show resolved Hide resolved
t/mojo/dom.t Outdated Show resolved Hide resolved
t/mojo/dom.t Outdated Show resolved Hide resolved
t/mojo/dom.t Show resolved Hide resolved
@kraih
Copy link
Member

kraih commented Jun 24, 2023

Please squash your commits. And split up individual bug fixes into separate PRs.

@kraih
Copy link
Member

kraih commented Jun 24, 2023

And for bug fixes where specs are relevant, please reference the according spec sections.

@poti1
Copy link
Author

poti1 commented Jun 26, 2023

Please squash your commits. And split up individual bug fixes into separate PRs.

Should I close this PR and open another with a single squashed branch per PR?

(Just noticed you already did reply back)

@poti1
Copy link
Author

poti1 commented Jun 26, 2023

And for bug fixes where specs are relevant, please reference the according spec sections.

You mean that I should include a comment with a link to the specific spec?

@poti1 poti1 closed this Jun 26, 2023
@poti1
Copy link
Author

poti1 commented Jun 26, 2023

Will open separate PRs

is $dom->tree->[7][1], '<', 'wrong comment';
is $dom->tree->[8][1], "!-- bad idea -- HTML4 -- >\n", 'wrong comment';

for ('<!-->', '<!--->', '<!-- --!>') {
Copy link
Member

Choose a reason for hiding this comment

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

$_ with such a wide scope is not good style.

Copy link
Member

Choose a reason for hiding this comment

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

In fact, i don't like loops in tests at all, they only make errors harder to find because line numbers get so much less useful.

@kraih
Copy link
Member

kraih commented Jun 26, 2023

In its current form this seems like it would have been fine as one single squashed PR.

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.

2 participants