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

feedback on pr 3518 #294

Merged
merged 1 commit into from
Apr 22, 2021
Merged

Conversation

peterbe
Copy link

@peterbe peterbe commented Apr 21, 2021

I started doing some reviewing and to back up my comments I started playing with the code.
Eventually, I had enough code that it would just be easier to send it over like this.

I'll explain some reasoning within.

}
});
console.log("HERE!!");
console.log(specifications);
Copy link
Author

Choose a reason for hiding this comment

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

Sorry. :)

return {
bcdSpecificationURL: specURL,
title: spec.title,
shortTitle: spec.shortTitle,
Copy link
Author

Choose a reason for hiding this comment

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

The TypeScript React code assumes that title and shortTitle is always a string. THis might not be safe! I haven't looked deeper into browser-specs but could it be that some entries in there have null on the shortTitle, for example? If so we need to guard better.

Copy link
Owner

Choose a reason for hiding this comment

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

They use a schema to validate their data https://github.com/w3c/browser-specs/blob/master/schema/definitions.json. So, shortTitle is defined as a string.

I don't really know a lot about TypeScript but maybe it would make sense if browser-specs had a TypeScript definition file? I know BCD has this for that reason, too.

Copy link
Owner

@Elchi3 Elchi3 left a comment

Choose a reason for hiding this comment

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

This looks all very reasonable to me. I'll merge this, so we can continue the conversation upstream

@Elchi3 Elchi3 merged commit 0d4e4ac into Elchi3:prototype-spectable Apr 22, 2021
@peterbe peterbe deleted the feedback-on-pr-3518 branch April 22, 2021 13:18
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