Skip to content

Conversation

@karlseguin
Copy link
Collaborator

There is some risk to this change. The first is that I made a mistake. The other is that one of the APIs that doesn't currently return an error changes in the future.

There is some risk to this change. The first is that I made a mistake. The
other is that one of the APIs that doesn't currently return an error changes
in the future.
Copy link
Member

@krichprollsch krichprollsch left a comment

Choose a reason for hiding this comment

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

2 non-blocking comments

return parser.nodeGetPrefix(parser.attributeToNode(self));
}

pub fn get_localName(self: *parser.Attribute) ![]const u8 {
Copy link
Member

Choose a reason for hiding this comment

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

you don't remove the error return here on purpose? (same for the 2 following)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

The underlying netsurf function still returns an error, I just removed the redundant try.

const Browser = @import("browser/browser.zig").Browser;

const build_config = @import("build_config");
const parser = @import("browser/netsurf.zig");
Copy link
Member

Choose a reason for hiding this comment

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

Do you use something auto to cleanup imports? or it's manual?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I used https://github.com/DonIsaac/zlint I was hoping it would help me find error return types that didn't need to be, but it doesn't detect that I guess. And I couldn't help myself but also remove these imports when I saw it.

@karlseguin karlseguin merged commit 024f7ad into main Sep 18, 2025
10 checks passed
@karlseguin karlseguin deleted the DOM_NO_ERR branch September 18, 2025 11:06
@github-actions github-actions bot locked and limited conversation to collaborators Sep 18, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants