perf(Component UI): lazy load component logs #7346
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
Legacy Bit
loadComponentLogs
to accept a list of refs tostopAt
collectLogs
onModelComponent
to forwardstopAt
ref filter togetAllVersionsInfo
BIT
getLogs
onScopeMain
to allow filtering logs withhead?: string
startFrom?: string
stopAt?: string
startFromOffset?: number
stopAtOffset?: number
type?: 'snap' | 'tag'
findNodeByOffset
to find the closest node to an offset in a Version graphuntil
,startFrom
,head
,limit
,type (snap or tag)
UI
useComponentQuery
to allow lazy loading component logsuseComponentLogs
hookComponentCompare
fullScreen default modeLanesUI
refactorLanesSwitcher
fix loading stateCodeUI
allow overriding css for code snippets