improvement(doc-tags-subblock): use table for doc tags subblock in create_document tool for KB

[icecrasher321]

Description

Existing UI for KB Block Create Document Tool to add tags not great + doesn't work with dark mode.

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

New UI uses Table format as suggested

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added tests that prove my fix is effective or that my feature works
• All tests pass locally and in CI (bun run test)
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules
• I have updated version numbers as needed (if needed)
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Security Considerations:

• My changes do not introduce any new security vulnerabilities
• I have considered the security implications of my changes

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sim	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 30, 2025 8:01pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Skipped (Inspect)			Jul 30, 2025 8:01pm

[greptile-apps]

Greptile Summary

This PR completely refactors the document tag entry component for the knowledge base's create_document tool, replacing the existing list-based interface with a table-based design. The change addresses dark mode compatibility issues and improves the overall user experience.

The major transformation includes:

• Data Structure Change: Migrated from DocumentTag interface to DocumentTagRow with nested cells object containing tagName, type, and value properties
• UI Architecture: Replaced custom list sections (available/selected tags) with a structured table using header and cell rendering functions
• Enhanced Functionality: Added tag name autocomplete with dropdown states, prefill functionality for existing tags, and duplicate detection logic
• Constraint Removal: Eliminated the MAX_TAG_SLOTS limitation, allowing unlimited tag entries
• Improved UX: Better organization of tag data in tabular format with consistent styling that supports dark mode

The component now uses established table patterns from the codebase rather than custom layouts, integrating with existing TagDropdown functionality for autocomplete suggestions. The change maintains the same external API while significantly improving the internal structure and user interface.

Confidence score: 2/5

• This PR has several concerning implementation issues that could cause runtime errors and poor user experience
• Multiple instances of JSON parsing without proper error handling could crash the component, and complex state management with race conditions could lead to inconsistent behavior
• The file apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/workflow-block/components/sub-block/components/document-tag-entry/document-tag-entry.tsx needs significant attention for error handling and state management improvements

_{1 file reviewed, 2 comments}

_{Edit Code Review Bot Settings | Greptile}

[greptile-apps]

logic: JSON.parse could throw an error if currentValue is malformed. Should wrap in try-catch like lines 64-78.

Suggested change

	const currentData = currentValue ? JSON.parse(currentValue) : []
	const currentData = currentValue ? (() => {
	try {
	return JSON.parse(currentValue)
	} catch {
	return []
	}
	})() : []