Skip to content

Conversation

@labkey-susanh
Copy link

Rationale

Since there's nothing specific about assays in the findUniqueFileName method (and relatives), they are better located in the FileUtil class than AssayFileWriter.

Related Pull Requests

Changes

  • Adjust location for findUniqueFileName method.

@labkey-susanh labkey-susanh requested a review from cnathe July 24, 2025 17:32
@labkey-susanh labkey-susanh merged commit d4963ec into develop Jul 30, 2025
7 of 9 checks passed
@labkey-susanh labkey-susanh deleted the fb_fileNameAudit branch July 30, 2025 19:34
public @Nullable Double getSchemaVersion()
{
return 23.000;
return 25.000;

Choose a reason for hiding this comment

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

@labkey-susanh was this schema bump necessary for some reason?

Copy link
Author

Choose a reason for hiding this comment

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

No. I had thought so initially, but it wasn't. Is it causing issues?

Choose a reason for hiding this comment

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

No, just unusual for us to be bumping versions in modules we don't manage. If deployed without any other upgrading modules, it will cause a no-op "upgrade" (drop and recreate all views), but that's harmless.

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