Skip to content

Conversation

@labkey-klum
Copy link
Contributor

Rationale

https://github.com/LabKey/internal-issues/issues/685

This adds a WebParts column to the core.containers table to track webparts per container. Additionally we are removing the recently added ActiveFolders column from core.modules. The equivalent information was already available as ActiveModules in core.containers but went largely unnoticed because it was hidden.

Both WebParts and ActiveModules are not hidden but will not be included in the default view.

…ality for modules per container from the modules table.
@labkey-klum labkey-klum self-assigned this Jan 8, 2026
@labkey-klum labkey-klum requested a review from a team January 8, 2026 21:00
Copy link
Contributor

@labkey-jeckels labkey-jeckels left a comment

Choose a reason for hiding this comment

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

This looks fine, but I'm not seeing test coverage. Seems like it should be simple to check the values in an existing automated test that's done some setup.

.append(" FROM ").append(Portal.getTableInfoPortalWebParts(), "PWP")
.append(" WHERE PWP.container = " + ExprColumn.STR_TABLE_ALIAS + ".entityId)");
ExprColumn webpartColumn = new ExprColumn(this, "WebParts", webpartNamesSQL, JdbcType.VARCHAR);
webpartColumn.setReadOnly(true);
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this needed? I hope ExprColumns are considered read only by default

Copy link
Contributor Author

Choose a reason for hiding this comment

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

probably not, it just affect how the column metadata is reported in the table summary view.

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