Remove isScratch banner

[philippotto]

Hasn't been used in 5 years.

[coderabbitai]

📝 Walkthrough

📝 Walkthrough

Walkthrough

The pull request modifies the TracingLayoutView component in the frontend, specifically removing references to dataset scratch volume warnings. The changes involve eliminating the isDatasetOnScratchVolume property from both the component's props and the mapStateToProps function. Import statements for WarningFilled and Alert have been removed, and the associated conditional rendering for dataset warning alerts has been eliminated, simplifying the component's rendering logic.

Changes

File	Change Summary
frontend/javascripts/oxalis/view/layouting/tracing_layout_view.tsx	- Removed isDatasetOnScratchVolume from props destructuring - Removed isDatasetOnScratchVolume from mapStateToProps - Deleted imports for WarningFilled and Alert - Removed conditional alert rendering for scratch volume warnings

Possibly related PRs

• Wrap antd tree to enable scrolling while dragging #8162: Modifies the TracingLayoutView component by changing the import path for the importTracingFiles function.
• Fix: Use forwardRef for scrollable virtualized tree #8186: Addresses the ScrollableVirtualizedTree component, related to UI components and rendering logic.
• Add total voxel count and dataset extent to tooltip in dataset info tab #8229: Adds a tooltip displaying the total volume of a dataset in the dataset info tab, relevant to UI updates.
• Only show locked banner if current user is in organization of the annotation #8273: Modifies the navbar to conditionally display the locked banner based on organizational context, relating to user interface improvements.

Suggested labels

bug, documentation

Suggested reviewers

• hotzenklotz
• normanrz

Poem

🐰 A layout view, stripped bare and clean,
No warnings dance across the screen
Scratch volumes fade, alerts take flight
Simplicity emerges, crisp and bright
Code hops forward, lean and free! 🚀

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7866b11 and 1439e98.

📒 Files selected for processing (1)

• CHANGELOG.unreleased.md (1 hunks)

🔇 Additional comments (1)

CHANGELOG.unreleased.md (1)

42-42: LGTM! Well-documented changelog entry.

The changelog entry is clear, follows the proper format, and accurately describes the removal of the scratch volume warning feature. It's appropriately placed in the "Removed" section and includes the correct PR reference.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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.

[fm3]

LGTM and works for me too :) Thanks!

Could you add a changelog entry?

[MichaelBuessemeyer]

Maybe also remove the property from the frontend as this is the onliest place where it is actively used?