Skip to content

Conversation

@labkey-jeckels
Copy link
Contributor

Rationale

Add a new vet user and group as part of automated test setup. Clear many IntelliJ warnings.

Changes

  • Clean up generics
  • Misc other code cleanup
  • Add vet user and group
  • Include both site and project groups when populating the ehr_lookups.veterinarian table

{
Group assignedGroup = SecurityManager.getGroup(r.getUserId());
if (assignedGroup != null && !assignedGroup.isProjectGroup())
if (assignedGroup != null)
Copy link
Contributor

Choose a reason for hiding this comment

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

Not really sure what the original use case was here. I don't see anyone using vets that wouldn't be listed in EHR or having different permissions at project level.

Copy link
Collaborator

Choose a reason for hiding this comment

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

I assume I wrote that, but it's been too long to recall. I cannot think of any reason to differentiate between site groups and project-level groups. If no center is actually using a project-level group in this table then it's a moot point and probably doesnt need to exist.

Given how long ago this was, it's equally likely that some long-ago quirk the in SecurityManager API required this kind of check for some reason.

@labkey-jeckels labkey-jeckels merged commit 24c3938 into release24.11-SNAPSHOT Mar 20, 2025
3 of 5 checks passed
@labkey-jeckels labkey-jeckels deleted the 24.11_fb_ssrsSessionId branch March 20, 2025 20:12
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.

4 participants