Skip to content

Comments

UFAL/Fetching preview item data only when necessary#1007

Open
jr-rk wants to merge 1 commit intodtq-devfrom
ufal/optional-file-preview-before-fetching
Open

UFAL/Fetching preview item data only when necessary#1007
jr-rk wants to merge 1 commit intodtq-devfrom
ufal/optional-file-preview-before-fetching

Conversation

@jr-rk
Copy link

@jr-rk jr-rk commented Jul 9, 2025

Phases MP MM MB MR JM Total
ETA 0 0 0 0 0 0
Developing 0 0 0 0 0 0
Review 0 0 0 0 0 0
Total - - - - - 0
ETA est. 0
ETA cust. - - - - - 0

Problem description

Items are prefetching their previews even without "preview" button clicked, it is unnecessary.

Reported issues

ufal#1212

Summary by CodeRabbit

  • Refactor
    • Improved the way file information is constructed and managed, allowing for more flexible assignment of file structure details. No changes to visible features or user interface.

@jr-rk jr-rk self-assigned this Jul 9, 2025
@coderabbitai
Copy link

coderabbitai bot commented Jul 9, 2025

Walkthrough

The changes refactor the way the FileInfo class handles its sub field. The constructor no longer accepts the sub map; instead, a setter method is introduced for this purpose. Correspondingly, the PreviewContentServiceImpl class is updated to construct FileInfo objects without passing the sub map.

Changes

File(s) Change Summary
dspace-api/src/main/java/org/dspace/util/FileInfo.java Removed sub parameter from constructor; added setSub method to set sub after construction.
dspace-api/src/main/java/org/dspace/content/PreviewContentServiceImpl.java Updated createFileInfo to construct FileInfo without the sub map.

Poem

A bunny hopped through code today,
Refactoring fields along the way.
Constructors slimmed, setters appear,
The sub map’s path is now more clear!
With every hop, the structure’s neat—
In Java fields, the changes meet.
🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Nitpick comments (1)
dspace-api/src/main/java/org/dspace/util/FileInfo.java (1)

18-23: Consider encapsulation improvements.

The public fields violate encapsulation principles and could lead to uncontrolled access to internal state.

Consider making fields private and providing appropriate getter methods:

-public String name;
-public String content;  
-public String size;
-public boolean isDirectory;
-public Hashtable<String, FileInfo> sub = null;
+private String name;
+private String content;
+private String size;
+private boolean isDirectory;
+private Hashtable<String, FileInfo> sub = null;

+public String getName() { return name; }
+public String getContent() { return content; }
+public String getSize() { return size; }
+public boolean isDirectory() { return isDirectory; }
+public Hashtable<String, FileInfo> getSub() { return sub; }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1418519 and c608b70.

📒 Files selected for processing (2)
  • dspace-api/src/main/java/org/dspace/content/PreviewContentServiceImpl.java (1 hunks)
  • dspace-api/src/main/java/org/dspace/util/FileInfo.java (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: dspace-dependencies / docker-build (linux/amd64, ubuntu-latest, true)
  • GitHub Check: Run Unit Tests
  • GitHub Check: Run Integration Tests
🔇 Additional comments (1)
dspace-api/src/main/java/org/dspace/util/FileInfo.java (1)

25-30: Constructor change looks good for lazy loading optimization.

The removal of the sub parameter from the constructor aligns with the PR objective to fetch preview data only when necessary. This supports lazy loading of hierarchical file structure data.

Comment on lines +48 to +50
public void setSub(Hashtable<String, FileInfo> sub) {
this.sub = sub;
}
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Add validation to the setter method.

The setter method lacks validation and could potentially cause issues if called with invalid data.

 public void setSub(Hashtable<String, FileInfo> sub) {
+    if (sub != null && !isDirectory) {
+        throw new IllegalStateException("Cannot set sub for non-directory FileInfo");
+    }
     this.sub = sub;
 }
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
public void setSub(Hashtable<String, FileInfo> sub) {
this.sub = sub;
}
public void setSub(Hashtable<String, FileInfo> sub) {
if (sub != null && !isDirectory) {
throw new IllegalStateException("Cannot set sub for non-directory FileInfo");
}
this.sub = sub;
}
🤖 Prompt for AI Agents
In dspace-api/src/main/java/org/dspace/util/FileInfo.java around lines 48 to 50,
the setSub setter method currently assigns the input parameter directly without
validation. Add validation to check if the provided Hashtable<String, FileInfo>
sub is not null before assigning it to this.sub. If the input is invalid (e.g.,
null), handle it appropriately by either throwing an IllegalArgumentException or
ignoring the assignment to prevent potential issues.

Comment on lines 202 to 205
public FileInfo createFileInfo(PreviewContent pc) {
Hashtable<String, FileInfo> sub = createSubMap(pc.sub, this::createFileInfo);
return new FileInfo(pc.name, pc.content, pc.size, pc.isDirectory, sub);
return new FileInfo(pc.name, pc.content, pc.size, pc.isDirectory);
}
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Critical: Missing assignment of sub map to FileInfo object.

The sub map is created on line 203 but never assigned to the FileInfo object. This will break the hierarchical structure of file previews as the sub-directory/file relationships will be lost.

 public FileInfo createFileInfo(PreviewContent pc) {
     Hashtable<String, FileInfo> sub = createSubMap(pc.sub, this::createFileInfo);
-    return new FileInfo(pc.name, pc.content, pc.size, pc.isDirectory);
+    FileInfo fileInfo = new FileInfo(pc.name, pc.content, pc.size, pc.isDirectory);
+    fileInfo.setSub(sub);
+    return fileInfo;
 }
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
public FileInfo createFileInfo(PreviewContent pc) {
Hashtable<String, FileInfo> sub = createSubMap(pc.sub, this::createFileInfo);
return new FileInfo(pc.name, pc.content, pc.size, pc.isDirectory, sub);
return new FileInfo(pc.name, pc.content, pc.size, pc.isDirectory);
}
public FileInfo createFileInfo(PreviewContent pc) {
Hashtable<String, FileInfo> sub = createSubMap(pc.sub, this::createFileInfo);
FileInfo fileInfo = new FileInfo(pc.name, pc.content, pc.size, pc.isDirectory);
fileInfo.setSub(sub);
return fileInfo;
}
🤖 Prompt for AI Agents
In dspace-api/src/main/java/org/dspace/content/PreviewContentServiceImpl.java
around lines 202 to 205, the sub map created by createSubMap is not assigned to
the FileInfo object, causing loss of hierarchical structure. Modify the code to
assign the sub map to the FileInfo instance, either by passing it to the
constructor if supported or by setting it via a setter method after creating the
FileInfo object.

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