Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

include non-user editable columns in details view #812

Draft
wants to merge 10 commits into
base: develop
Choose a base branch
from

Conversation

labkey-kevink
Copy link
Contributor

  • include non-user editable columns details view by default
  • infer column 'showInDetailsView' unless explicitly set
  • validate queries checks for QueryView without detailsURL with showDetailsColumn=true

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.

Maybe fine as-is, but a couple of questions.

@@ -40,6 +41,10 @@
*/
public abstract class ColumnRenderPropertiesImpl implements ColumnRenderProperties
{
protected static final Set<String> NON_EDITABLE_COL_NAMES = new CaseInsensitiveHashSet(
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's wrap this in a Collections.unmodifiableSet(). It should preserve the case-insensitive semantics, but I've heard that immutability is good...

@@ -45,7 +45,7 @@ public UpdateView(TableViewForm form, BindException errors)
@Override
protected boolean isColumnIncluded(ColumnInfo col)
{
return col.isShownInUpdateView();
return col.isUserEditable() && col.isShownInUpdateView();
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need this check? I feel like there are a few cases where we want to show a read-only view of some columns, but I can't conjure up a concrete example either.

@labkey-kevink labkey-kevink marked this pull request as draft November 4, 2020 03:03
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