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

Category Labels Not Scaling Correctly On Small Screen #3906

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

annechoww
Copy link

@annechoww annechoww commented Nov 27, 2024

Fixes #3849

Category Labels should now scale alongside the background on smaller screens. See fix below:

image

Copy link

netlify bot commented Nov 27, 2024

Deploy Preview for actualbudget ready!

Name Link
🔨 Latest commit dd3ac55
🔍 Latest deploy log https://app.netlify.com/sites/actualbudget/deploys/67477f4f5bd4620008ea915a
😎 Deploy Preview https://deploy-preview-3906.demo.actualbudget.org
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

github-actions bot commented Nov 27, 2024

Bundle Stats — desktop-client

Hey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle.

As this PR is updated, I'll keep you updated on how the bundle size is impacted.

Total

Files count Total bundle size % Changed
10 5.45 MB → 5.45 MB (+113 B) +0.00%
Changeset
File Δ Size
src/components/transactions/TransactionsTable.jsx 📈 +113 B (+0.17%) 66.88 kB → 66.99 kB
View detailed bundle breakdown

Added

No assets were added

Removed

No assets were removed

Bigger

Asset File Size % Changed
static/js/wide.js 241.19 kB → 241.3 kB (+113 B) +0.05%

Smaller

No assets were smaller

Unchanged

Asset File Size % Changed
static/js/indexeddb-main-thread-worker-e59fee74.js 13.5 kB 0%
static/js/workbox-window.prod.es5.js 5.69 kB 0%
static/js/useAccountPreviewTransactions.js 1.68 kB 0%
static/js/resize-observer.js 18.37 kB 0%
static/js/BackgroundImage.js 122.29 kB 0%
static/js/narrow.js 82.93 kB 0%
static/js/AppliedFilters.js 21.32 kB 0%
static/js/ReportRouter.js 1.52 MB 0%
static/js/index.js 3.44 MB 0%

Copy link
Contributor

github-actions bot commented Nov 27, 2024

Bundle Stats — loot-core

Hey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle.

As this PR is updated, I'll keep you updated on how the bundle size is impacted.

Total

Files count Total bundle size % Changed
1 1.32 MB 0%

Changeset

No files were changed

View detailed bundle breakdown

Added

No assets were added

Removed

No assets were removed

Bigger

No assets were bigger

Smaller

No assets were smaller

Unchanged

Asset File Size % Changed
kcab.worker.js 1.32 MB 0%

@annechoww annechoww changed the title [WIP] Category Labels Not Scaling Correctly On Small Screen Category Labels Not Scaling Correctly On Small Screen Nov 27, 2024
Copy link
Contributor

coderabbitai bot commented Nov 27, 2024

Walkthrough

The pull request introduces modifications to the TransactionsTable.jsx component, enhancing the rendering and management of transaction data. Key updates include new styles for the category field to improve text overflow handling and an updated CategoryAutocomplete component that includes a showSplitOption prop for better management of split transactions. The Transaction component has improved logic for handling temporary transactions, featuring a new makeTemporaryTransactions function that generates temporary transaction objects with default values. Additionally, the onUpdate function has been modified to include checks for reconciled transactions, ensuring appropriate warnings are displayed during edits. The TransactionTableInner component has been updated to render new transactions more effectively, introducing a NewTransaction component for adding transactions with enhanced user feedback. Error handling related to split transactions has also been refined, resulting in clearer logic for error messages and user interactions.

Assessment against linked issues

Objective Addressed Explanation
Category background tags should scale correctly on small screens (3849)

Possibly related PRs

Suggested labels

:sparkles: Merged

Suggested reviewers

  • matt-fidd
  • MikesGlitch

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 eslint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

packages/desktop-client/src/components/transactions/TransactionsTable.jsx

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-eslint-plugin".

(The package "eslint-plugin-eslint-plugin" was not found when loaded as a Node module from the directory "/packages/eslint-plugin-actual".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-eslint-plugin@latest --save-dev

The plugin "eslint-plugin-eslint-plugin" was referenced from the config file in "packages/eslint-plugin-actual/.eslintrc.js".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.


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 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
Contributor

@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 and nitpick comments (4)
packages/desktop-client/src/components/transactions/TransactionsTable.jsx (4)

Line range hint 273-279: Simplify the selectAscDesc function for improved readability

The nested ternary operators in the selectAscDesc function can reduce readability and make the code harder to maintain. Consider refactoring it using if-else statements or simplifying the ternary expressions.

Here's a possible refactor:

function selectAscDesc(field, ascDesc, clicked, defaultAscDesc = 'asc') {
-  return field === clicked
-    ? ascDesc === 'asc'
-      ? 'desc'
-      : 'asc'
-    : defaultAscDesc;
+  if (field === clicked) {
+    return ascDesc === 'asc' ? 'desc' : 'asc';
+  } else {
+    return defaultAscDesc;
+  }
}

Line range hint 727-1133: Refactor the Transaction component to enhance maintainability

The Transaction component spans over 400 lines and handles multiple responsibilities, including rendering, state management, and event handling. This complexity can make the component difficult to understand, test, and maintain. Consider breaking it down into smaller, reusable components to improve readability and adhere to the Single Responsibility Principle.


Line range hint 822-865: Prevent potential multiple calls in onUpdate function

The onUpdate function includes checks to prevent multiple modal displays, but there might still be scenarios where it gets called multiple times unintentionally. This can lead to inconsistent state or unexpected behaviors.

Consider implementing a debounce or throttling mechanism, or revising the condition checks to ensure onUpdate is called only when necessary.


Line range hint 1355-1370: Optimize makeTemporaryTransactions function for future scalability

Currently, the makeTemporaryTransactions function returns an array with a single temporary transaction. If there is a future requirement to generate multiple temporary transactions, consider adjusting the function to accept a parameter specifying the number of transactions to create.

For example:

-function makeTemporaryTransactions(currentAccountId, currentCategoryId, lastDate) {
+function makeTemporaryTransactions(currentAccountId, currentCategoryId, lastDate, count = 1) {
+  return Array.from({ length: count }, (_, index) => ({
     id: 'temp',
     date: lastDate || currentDay(),
     account: currentAccountId || null,
     category: currentCategoryId || null,
     cleared: false,
     amount: null,
+    index,
   }));
 }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 22623ce and dd3ac55.

⛔ Files ignored due to path filters (1)
  • upcoming-release-notes/3906.md is excluded by !**/*.md
📒 Files selected for processing (1)
  • packages/desktop-client/src/components/transactions/TransactionsTable.jsx (1 hunks)
🔇 Additional comments (1)
packages/desktop-client/src/components/transactions/TransactionsTable.jsx (1)

Line range hint 1606-1665: Verify edge case handling in notesTagFormatter function

The notesTagFormatter function processes note tags within the notes text. Ensure that it correctly handles edge cases, such as multiple consecutive '#' characters, empty tags, or special characters, to prevent potential rendering issues or errors.

To verify this, consider adding unit tests covering scenarios like:

  • Notes with multiple consecutive '#' characters (e.g., ###tag)
  • Notes with tags containing special characters or spaces
  • Notes with empty tags or trailing '#' characters

This will help ensure the function behaves correctly in all cases.

Copy link
Contributor

@matt-fidd matt-fidd left a comment

Choose a reason for hiding this comment

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

Thanks for this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Category Labels Not Scaling Correctly On Small Screen
2 participants