Skip to content

Conversation

@mofojed
Copy link
Member

@mofojed mofojed commented Jan 19, 2026

@gzh2003 @mattrunyon take a look at the proposal in the DH-21375 planning document as part of this PR and see if you have any comments about it. Can try playing with databars as they are currently to help inform your opinion: https://deephaven.io/core/ui/docs/components/table/#formatting-databars

Create comprehensive plan document for integrating databars into ui.TableFormat:

  • Align databars with other formatting features for API consistency
  • Enable conditional databars with if_ parameter support
  • Maintain backward compatibility with deprecated databars parameter
  • Define 5-phase implementation: foundation, JS integration, testing, docs, cleanup
  • Document testing strategy, migration guide, and success criteria
  • Address open design questions with recommendations

Add comprehensive guide for AI agents working in the deephaven-plugins repository covering:
- Environment setup (Python and JavaScript)
- Building plugins (Python wheels and JS bundles)
- Running unit tests (tox) and E2E tests (Playwright)
- Running development server (deephaven-core and Docker)
- Documentation preview and snapshot generation
- Code quality and pre-commit hooks
- Common development workflows
- Release management

Prioritizes local development workflows over Docker-based approaches.
Add feature planning infrastructure:
- Create plugins/ui/plans/ directory for feature plan documents
- Add README with naming convention (ticket number + keyword)
- Define plan document structure (overview, goals, design, implementation, testing, docs, open questions)
- Update AGENTS.md with general instructions for creating feature plans in any plugin
…rmat

Create comprehensive plan document for integrating databars into ui.TableFormat:
- Align databars with other formatting features for API consistency
- Enable conditional databars with if_ parameter support
- Maintain backward compatibility with deprecated databars parameter
- Define 5-phase implementation: foundation, JS integration, testing, docs, cleanup
- Document testing strategy, migration guide, and success criteria
- Address open design questions with recommendations
@mofojed mofojed requested review from gzh2003 and mattrunyon January 19, 2026 19:37
@mofojed mofojed self-assigned this Jan 19, 2026
@github-actions
Copy link

Pull Request titles must follow the Conventional Commits specification.

Details:

Unknown release type "plan" found in pull request title "plan: add feature plan for DH-21375 databars integration with TableFormat". 

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

@dsmmcken
Copy link
Contributor

Whatever you come up with, keep in mind the heatmap function will likely share like 70% of the same props (min/max/colors[]/value_column etc.) Ideally, a single change could switch between the two.

Just take that into consideration.

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.

2 participants