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

feat(ui): runs & robots loader #358

Merged
merged 8 commits into from
Jan 18, 2025
Merged

feat(ui): runs & robots loader #358

merged 8 commits into from
Jan 18, 2025

Conversation

amhsirak
Copy link
Member

@amhsirak amhsirak commented Jan 17, 2025

No description provided.

Copy link

coderabbitai bot commented Jan 17, 2025

Walkthrough

The pull request introduces loading indicators to two table components: RecordingsTable and RunsTable. These changes enhance user experience by adding visual feedback when data is being fetched or when no recordings/runs are available. By utilizing Material-UI's CircularProgress component, the modifications provide a centered loading spinner when the respective data arrays are empty, improving the overall interface clarity.

Changes

File Change Summary
src/components/robot/RecordingsTable.tsx Added CircularProgress for loading state when no recordings are present
src/components/run/RunsTable.tsx Implemented CircularProgress to indicate data loading when rows are empty

Sequence Diagram

sequenceDiagram
    participant User
    participant Component
    participant DataSource
    
    User->>Component: Loads Page
    Component->>DataSource: Fetch Data
    alt Data Loading
        Component->>User: Display CircularProgress
    else Data Loaded
        Component->>User: Render Table
    end
Loading

Poem

🐰 Loading, loading, spinning round,
A rabbit's progress bar is found!
No more waiting in the dark,
Our UI now has a loading spark!
Data comes, just hang tight! 🌟


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
🪧 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.

@amhsirak amhsirak added the Scope: UI/UX Issues/PRs related to UI/UX label Jan 17, 2025
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: 0

🔭 Outside diff range comments (1)
src/components/robot/RecordingsTable.tsx (1)

Line range hint 108-110: Align error handling with RunsTable.

The error case only logs to console, while RunsTable uses the notify system. Consider using consistent error handling across components.

   } else {
-    console.log('No recordings found.');
+    notify('error', t('recordingtable.notifications.no_recordings'));
   }
🧹 Nitpick comments (3)
src/components/run/RunsTable.tsx (2)

163-167: Consider improving the loading state handling.

The current implementation might lead to a brief flash of the loading indicator during initial load, and doesn't distinguish between "loading" and "no data" states.

Consider tracking the loading state explicitly:

+const [isLoading, setIsLoading] = useState(true);

 const fetchRuns = async () => {
+  setIsLoading(true);
   const runs = await getStoredRuns();
   if (runs) {
     const parsedRows: Data[] = runs.map((run: any, index: number) => ({
       id: index,
       ...run,
     }));
     setRows(parsedRows);
   } else {
     notify('error', t('runstable.notifications.no_runs'));
   }
+  setIsLoading(false);
 };

-{rows.length === 0 ? (
+{isLoading ? (
   <Box display="flex" justifyContent="center" alignItems="center" height="50%">
     <CircularProgress />
   </Box>
+) : rows.length === 0 ? (
+  <Box display="flex" justifyContent="center" alignItems="center" height="50%">
+    <Typography color="textSecondary">
+      {t('runstable.no_data', 'No runs available')}
+    </Typography>
   </Box>
 ) : (

164-164: Improve vertical centering consistency.

Using a percentage height might not provide consistent centering across different viewport sizes.

Consider using a fixed height or viewport units:

-<Box display="flex" justifyContent="center" alignItems="center" height="50%">
+<Box display="flex" justifyContent="center" alignItems="center" minHeight="400px">
src/components/robot/RecordingsTable.tsx (1)

203-207: Apply consistent loading state improvements.

Similar to RunsTable, consider improving the loading state handling to distinguish between "loading" and "no data" states.

Apply the same improvements suggested for RunsTable:

+const [isLoading, setIsLoading] = useState(true);

 const fetchRecordings = async () => {
+  setIsLoading(true);
   const recordings = await getStoredRecordings();
   if (recordings) {
     const parsedRows: Data[] = [];
     recordings.map((recording: any, index: number) => {
       if (recording && recording.recording_meta) {
         parsedRows.push({
           id: index,
           ...recording.recording_meta,
           content: recording.recording
         });
       }
     });
     setRecordings(parsedRows.map((recording) => recording.name));
     setRows(parsedRows);
   } else {
     console.log('No recordings found.');
   }
+  setIsLoading(false);
 }

-{rows.length === 0 ? (
+{isLoading ? (
   <Box display="flex" justifyContent="center" alignItems="center" height="50%">
     <CircularProgress />
   </Box>
+) : rows.length === 0 ? (
+  <Box display="flex" justifyContent="center" alignItems="center" height="50%">
+    <Typography color="textSecondary">
+      {t('recordingtable.no_data', 'No recordings available')}
+    </Typography>
   </Box>
 ) : (
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1060d64 and 395a352.

📒 Files selected for processing (2)
  • src/components/robot/RecordingsTable.tsx (2 hunks)
  • src/components/run/RunsTable.tsx (2 hunks)
🔇 Additional comments (2)
src/components/run/RunsTable.tsx (1)

12-12: LGTM! Clean import organization.

The CircularProgress component is correctly imported alongside other Material-UI components.

src/components/robot/RecordingsTable.tsx (1)

14-14: LGTM! Clean import organization.

The CircularProgress component is correctly imported alongside other Material-UI components.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: UI/UX Issues/PRs related to UI/UX
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant