Skip to content

[sc-14173] Implement the new simple Knowledge Box UI#2750

Merged
operramon merged 8 commits intomainfrom
oriolperramon8396/sc-14173/cowork-knowledge-layer-tier
Apr 22, 2026
Merged

[sc-14173] Implement the new simple Knowledge Box UI#2750
operramon merged 8 commits intomainfrom
oriolperramon8396/sc-14173/cowork-knowledge-layer-tier

Conversation

@operramon
Copy link
Copy Markdown
Contributor

No description provided.

@operramon operramon changed the title Oriolperramon8396/sc 14173/cowork knowledge layer tier [sc-14173] Support Cowork Knowledge tier Apr 15, 2026
@operramon operramon marked this pull request as ready for review April 16, 2026 10:30
@operramon operramon requested a review from a team as a code owner April 16, 2026 10:30
@operramon operramon marked this pull request as draft April 16, 2026 14:52
@operramon operramon force-pushed the oriolperramon8396/sc-14173/cowork-knowledge-layer-tier branch from 7257ac2 to a7594f3 Compare April 21, 2026 15:15
@operramon operramon changed the title [sc-14173] Support Cowork Knowledge tier [sc-14173] Implement new simple Knowledge Box UI Apr 22, 2026
@operramon operramon changed the title [sc-14173] Implement new simple Knowledge Box UI [sc-14173] Implement the new simple Knowledge Box UI Apr 22, 2026
@operramon operramon marked this pull request as ready for review April 22, 2026 14:52
@operramon operramon merged commit 163583f into main Apr 22, 2026
3 checks passed
@operramon operramon deleted the oriolperramon8396/sc-14173/cowork-knowledge-layer-tier branch April 22, 2026 17:06
</pa-table-cell>
<pa-table-cell header>
<span class="title-s">{{ 'simple.column.delete' | translate }}</span>
</pa-table-cell>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We can move headers into an array, and use @for here.

? 'error'
: resource.metadata?.status === RESOURCE_STATUS.PENDING
? 'pending'
: 'success') as TableRow['status'],
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We can create object like const statusMap = { [RESOURCE_STATUS.ERROR]: 'error', [RESOURCE_STATUS.PENDING]: 'pending', [RESOURCE_STATUS.SUCCESS]: 'success' } and set status like: status: statusMap[resource.metadata?.status]

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

ah, I will fix it. Now it's a bit verbose.

@if (step() === 1) {
{{ 'simple.title.first-files' | translate }}
} @else if (step() === 2) {
@if ((counter?.pending || 0) > 0 || (uploadInProgress | async)) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

It will be clearer to have a computed() variable in places like that

<strong [class.success]="counter?.pending === 0">{{ 'simple.ready' | translate }}</strong>
<span>: {{ counter?.processed || 0 }}</span>
</div>
@if ((counter?.pending || 0) > 0 || (uploadInProgress | async)) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

It will be clearer to have a computed() variable in places like that

@if (step() > 1) {
<div class="footer">
@if (step() === 2) {
@if (counter?.pending === 0 && !(uploadInProgress | async)) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

It will be clearer to have a computed() variable in places like that

map((processingStatus) =>
processingStatus.results
.reduce((resources, status) => {
if (status.schedule_order > -1) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Subtle thing, we can reduce nestedness in case like that
if (!x) return y ...

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.

3 participants