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

Add a report on external review status #3819

Merged
merged 12 commits into from
Apr 29, 2024

Conversation

jyasskin
Copy link
Collaborator

@jyasskin jyasskin commented Apr 25, 2024

There's a circular dependency in the generated openapi javascript, which is very similar to the one in OpenAPITools/openapi-generator#6140 but caused by using the discriminator field in the LinkPreview object. It doesn't appear to cause any concrete problems other than a warning during rollup, but I've sent OpenAPITools/openapi-generator#18503 to fix it in their repository.

gen/js/chromestatus-openapi/dist/esm/models/index.js -> gen/js/chromestatus-openapi/dist/esm/models/ExternalReviewsResponse.js -> gen/js/chromestatus-openapi/dist/esm/models/LinkPreview.js -> gen/js/chromestatus-openapi/dist/esm/models/index.js

Screenshot of the WebKit report:
Screenshot of WebKit reviewer report

api/converters.py Show resolved Hide resolved
api/external_reviews_api.py Outdated Show resolved Hide resolved
* @returns {number}
*/
function compareOutstandingReview(a, b) {
console.assert(a.current_stage === b.current_stage);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is this console.assert needed?

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 think I'd like to either keep it or turn it into an exception, although I'll add a better error message. The function doesn't do a reasonable sort on features whose current stages are different, so if the code ever changes to ask it to, we should notice that somehow. I lean toward a console message rather than an exception, because a bad sort doesn't make the page useless, and an exception probably would.

: nothing
),
error: e => {
console.error(e);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do you want to keep this console.error?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, since this branch results in a useless page, and people who encounter it should have a message they can paste to us in their bug report. But I should give it a better error message.

Copy link
Collaborator

@jcscottiii jcscottiii left a comment

Choose a reason for hiding this comment

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

LGTM

@jyasskin jyasskin merged commit 285d520 into GoogleChrome:main Apr 29, 2024
7 checks passed
@jyasskin jyasskin deleted the external-reviewer-status branch April 29, 2024 20:17
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