-
Notifications
You must be signed in to change notification settings - Fork 15
Add JetStreamParams #171
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
base: main
Are you sure you want to change the base?
Add JetStreamParams #171
Conversation
✅ Deploy Preview for webkit-jetstream-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
side-note: once we have this, I can also copy over the dev-menu from speedometer, which makes these parameters a bit more accessible. |
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.
Overall LGTM, some nits.
The high-level motivation (besides adding a UI menu in the browser later) seems to be (i) refactoring/cleanup and (ii) allowing detection of non-standard parameters, such that we can warn somehow when displaying results.
console.log(" ", tagName); | ||
console.log(""); | ||
|
||
if (typeof benchmarksByTag !== "undefined") { |
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.
Why this check, isn't benchmarksByTag
always defined in
Line 2634 in f8e3d7e
const benchmarksByTag = new Map(); |
In that case, can this just be an assert?
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.
LGTM with question.
constructor(sourceParams = undefined) { | ||
if (sourceParams) | ||
this._copyFromSearchParams(sourceParams); | ||
if (!this.developerMode) |
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.
You removed developer mode from the CLI options above, but not here. Is this intended? I'm still not sure I got the intuition behind the developer mode, how is it different / what does it ensure additionally on top of just warning when folks run JetStream with non-default parameters?
For displaying a warning about non-default params we need a way to keep track of what the default values are.
We can reuse the existing code from Speedometer which does exactly that.