Skip to content

Use proper renderer for custom metadata columns (#75)#94

Merged
tonygermano merged 1 commit intoOpenIntegrationEngine:mainfrom
sbraconnier:feature/dashboard-custom-metadata
Jul 1, 2025
Merged

Use proper renderer for custom metadata columns (#75)#94
tonygermano merged 1 commit intoOpenIntegrationEngine:mainfrom
sbraconnier:feature/dashboard-custom-metadata

Conversation

@sbraconnier
Copy link
Contributor

@sbraconnier sbraconnier commented May 17, 2025

Closes 75 / original 6203.

…browser

This fixes what was apparently a regression bug in Mirth 3.2.0
introduced by commit 70eba57. It
restores the functionality to display the contents of custom metadata
columns in a format appropriate to the column type rather than always
using the default MessageBrowserTextCellRenderer for non-String types.

Signed-off-by: Tony Germano <tony@germano.name>
Commit-message-by: Tony Germano <tony@germano.name>
Issue: OpenIntegrationEngine#75
Related: nextgenhealthcare/connect#6203
@tonygermano tonygermano force-pushed the feature/dashboard-custom-metadata branch from d053504 to 8e51433 Compare July 1, 2025 04:01
Copy link
Member

@tonygermano tonygermano left a comment

Choose a reason for hiding this comment

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

Rebased, tested, and fleshed out commit message. Looks good to me.

@tonygermano tonygermano merged commit 8e51433 into OpenIntegrationEngine:main Jul 1, 2025
2 checks passed
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.

[BUG] Custom metadata columns are always formatted using toString() in the message browser.

4 participants