-
Notifications
You must be signed in to change notification settings - Fork 12
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
feat(URL): Add support to query timestamp by URL #152
base: main
Are you sure you want to change the base?
Conversation
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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 structure looks really good
const mid = Math.floor((low + high) / 2); | ||
|
||
// @ts-expect-error TS2532: Object is possibly 'undefined'. | ||
const midTimestamp = this.#logEvents[mid].timestamp.valueOf(); |
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.
Since @ts-expect-error
disables type-checking for the whole following line, can we extract a const midLogEvent = this.#logEvents[mid];
and only disable type-checking for that?
@@ -137,6 +137,14 @@ onmessage = async (ev: MessageEvent<MainWorkerReqMessage>) => { | |||
args.isCaseSensitive | |||
); | |||
break; | |||
|
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.
Do we still need this?
const checkAndSetHashParam = (hashParamName: keyof UrlHashParams) => { | ||
const hashParam = hashParams.get(hashParamName); | ||
if (null !== hashParam) { | ||
const parsed = Number(hashParam); | ||
urlHashParams[hashParamName] = Number.isNaN(parsed) ? | ||
null : | ||
parsed; | ||
} | ||
}; | ||
|
||
checkAndSetHashParam(HASH_PARAM_NAMES.LOG_EVENT_NUM); | ||
checkAndSetHashParam(HASH_PARAM_NAMES.TIMESTAMP); |
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.
Would this be more concise and avoid the nested function declaration? (haven't tested
const checkAndSetHashParam = (hashParamName: keyof UrlHashParams) => { | |
const hashParam = hashParams.get(hashParamName); | |
if (null !== hashParam) { | |
const parsed = Number(hashParam); | |
urlHashParams[hashParamName] = Number.isNaN(parsed) ? | |
null : | |
parsed; | |
} | |
}; | |
checkAndSetHashParam(HASH_PARAM_NAMES.LOG_EVENT_NUM); | |
checkAndSetHashParam(HASH_PARAM_NAMES.TIMESTAMP); | |
const numberHashParamNames = [HASH_PARAM_NAMES.LOG_EVENT_NUM, HASH_PARAM_NAMES.TIMESTAMP]; | |
for (const paramName of numberHashParamNames) { | |
const hashParam = hashParams.get(paramName); | |
if (hashParam !== null) { | |
const parsed = Number(hashParam); | |
urlHashParams[paramName] = Number.isNaN(parsed) ? null : parsed; | |
} | |
} |
/** | ||
* Retrieves the last index of the log event that matches the given timestamp. | ||
* If no such log event exists, returns -1. | ||
* | ||
* @param timestamp | ||
* @return | ||
*/ |
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.
/** | |
* Retrieves the last index of the log event that matches the given timestamp. | |
* If no such log event exists, returns -1. | |
* | |
* @param timestamp | |
* @return | |
*/ | |
/** | |
* Finds the index of the last log event that matches the specified timestamp. | |
* | |
* @param timestamp | |
* @return The index of the matching log event, or -1 if no match is found. | |
*/ |
* @param timestamp | ||
* @return | ||
*/ | ||
getLogEventIdxByTimestamp(timestamp: number): number; |
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.
Shall we return null
no such event is found?
getLogEventIdxByTimestamp (timestamp: number): number { | ||
let low = 0; | ||
let high = this.#logEvents.length - 1; | ||
let result = -1; |
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.
let's see if the suggestion at https://github.com/y-scope/yscope-log-viewer/pull/152/files#r1890816021 makes sense. If not (i.e., we want to keep the return type as number
rather than Nullable<number>
), let's create a const for -1
so we can avoid magic numbers.
Description
Validation performed