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

♻️ (eslint) disallow importing actual-app/web in loot-core #4347

Merged
merged 1 commit into from
Feb 11, 2025

Conversation

MatissJanis
Copy link
Member

No description provided.

@actual-github-bot actual-github-bot bot changed the title ♻️ (eslint) disallow importing actual-app/web in loot-core [WIP] ♻️ (eslint) disallow importing actual-app/web in loot-core Feb 10, 2025
Copy link

netlify bot commented Feb 10, 2025

Deploy Preview for actualbudget ready!

Name Link
🔨 Latest commit a64f084
🔍 Latest deploy log https://app.netlify.com/sites/actualbudget/deploys/67aa621434839f0008c05974
😎 Deploy Preview https://deploy-preview-4347.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

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
16 6.83 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
static/js/workbox-window.prod.es5.js 5.69 kB 0%
static/js/resize-observer.js 18.37 kB 0%
static/js/useAccountPreviewTransactions.js 1.69 kB 0%
static/js/en-GB.js 99.33 kB 0%
static/js/wide.js 102.8 kB 0%
static/js/indexeddb-main-thread-worker-e59fee74.js 13.5 kB 0%
static/js/en.js 99.43 kB 0%
static/js/BackgroundImage.js 122.29 kB 0%
static/js/AppliedFilters.js 10.52 kB 0%
static/js/narrow.js 84.94 kB 0%
static/js/nl.js 94.83 kB 0%
static/js/uk.js 111.11 kB 0%
static/js/pt-BR.js 104.03 kB 0%
static/js/de.js 110.85 kB 0%
static/js/ReportRouter.js 1.59 MB 0%
static/js/index.js 4.29 MB 0%

Copy link
Contributor

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.33 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.33 MB 0%

@MatissJanis MatissJanis changed the title [WIP] ♻️ (eslint) disallow importing actual-app/web in loot-core ♻️ (eslint) disallow importing actual-app/web in loot-core Feb 10, 2025
Copy link
Contributor

coderabbitai bot commented Feb 10, 2025

Walkthrough

This pull request updates the ESLint configuration for the loot-core package to enforce stricter import boundaries. The changes modify the no-restricted-imports rule to prevent imports from the @actual-app/web package within the loot-core directory and enforce the use of relative paths instead of using pattern matching like loot-core/*. Additionally, inline comments have been added across various files to signal the need for future fixes related to these import restrictions. Several files now include imports of the useSyncedPref hook, accompanied by comments that highlight the intended restriction on importing from @actual-app/web. Despite these updates, the core functionality and existing method signatures of the affected modules remain unchanged.

Possibly related PRs

Suggested labels

:sparkles: Merged

Suggested reviewers

  • youngcw
  • jfdoming
✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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.

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: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4ee70e7 and a64f084.

⛔ Files ignored due to path filters (1)
  • upcoming-release-notes/4347.md is excluded by !**/*.md
📒 Files selected for processing (4)
  • eslint.config.mjs (1 hunks)
  • packages/loot-core/src/client/actions/prefs.ts (1 hunks)
  • packages/loot-core/src/client/data-hooks/schedules.tsx (1 hunks)
  • packages/loot-core/src/client/data-hooks/transactions.ts (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • packages/loot-core/src/client/actions/prefs.ts
  • packages/loot-core/src/client/data-hooks/transactions.ts
🔇 Additional comments (1)
eslint.config.mjs (1)

693-696: LGTM!

The ESLint rule correctly enforces the package boundary by disallowing imports from @actual-app/web in loot-core.

Comment on lines +11 to 12
// eslint-disable-next-line no-restricted-imports -- fix me -- do not import @actual-app/web in loot-core
import { useSyncedPref } from '@actual-app/web/src/hooks/useSyncedPref';
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Move preference management to loot-core.

The import from @actual-app/web violates the package boundary. Consider moving the preference management logic to loot-core to maintain proper separation of concerns.

Do you want me to help create a new preference management module within loot-core?

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.

LGTM!

@MatissJanis MatissJanis merged commit be1c194 into master Feb 11, 2025
20 checks passed
@MatissJanis MatissJanis deleted the matiss/eslint-actual-app-web-loot-core branch February 11, 2025 18:22
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.

2 participants