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

enhance: allow prefix for budget templates #4032

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

Conversation

UnderKoen
Copy link
Member

for example:
Prime video: #template $10

for example:
Prime video: #template $10
@actual-github-bot actual-github-bot bot changed the title enhance: allow prefix for budget templates [WIP] enhance: allow prefix for budget templates Dec 24, 2024
Copy link

netlify bot commented Dec 24, 2024

Deploy Preview for actualbudget ready!

Name Link
🔨 Latest commit 64daccb
🔍 Latest deploy log https://app.netlify.com/sites/actualbudget/deploys/676ae8dd5db15e0008128f02
😎 Deploy Preview https://deploy-preview-4032.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 Dec 24, 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.64 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/indexeddb-main-thread-worker-e59fee74.js 13.5 kB 0%
static/js/useAccountPreviewTransactions.js 1.63 kB 0%
static/js/workbox-window.prod.es5.js 5.69 kB 0%
static/js/AppliedFilters.js 10.24 kB 0%
static/js/resize-observer.js 18.37 kB 0%
static/js/BackgroundImage.js 122.29 kB 0%
static/js/narrow.js 83.36 kB 0%
static/js/wide.js 104.11 kB 0%
static/js/ReportRouter.js 1.58 MB 0%
static/js/index.js 3.71 MB 0%

Copy link
Contributor

github-actions bot commented Dec 24, 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 → 1.33 MB (+201 B) +0.01%
Changeset
File Δ Size
packages/loot-core/src/server/budget/goal-template.pegjs 📈 +584 B (+0.93%) 61.33 kB → 61.9 kB
packages/loot-core/src/server/budget/template-notes.ts 📈 +18 B (+0.66%) 2.67 kB → 2.69 kB
View detailed bundle breakdown

Added

No assets were added

Removed

No assets were removed

Bigger

Asset File Size % Changed
kcab.worker.js 1.32 MB → 1.33 MB (+201 B) +0.01%

Smaller

No assets were smaller

Unchanged

No assets were unchanged

@UnderKoen UnderKoen changed the title [WIP] enhance: allow prefix for budget templates enhance: allow prefix for budget templates Dec 24, 2024
Copy link
Contributor

coderabbitai bot commented Dec 24, 2024

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/loot-core/src/server/budget/template-notes.test.ts

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.

Walkthrough

The pull request introduces modifications to the budget template parsing logic across multiple files. In the goal-template.pegjs file, the grammar rules for limit and template were updated to provide more flexible parsing. The limit rule now returns a more consistent object structure for monthly cases, while the template rule now uses a regex pattern to match a broader range of inputs. In template-notes.ts, the template line identification logic was enhanced to allow for more flexible prefix matching using a regular expression. A corresponding test case was added to template-notes.test.ts to verify the new template parsing behavior, specifically testing scenarios with prefixed template notes.

Possibly related PRs

Suggested labels

sparkles: Merged

Suggested reviewers

  • youngcw

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.


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

🧹 Nitpick comments (1)
packages/loot-core/src/server/budget/template-notes.ts (1)

85-85: Ensure robust prefix handling and clarity in regex usage

Switching from startsWith(TEMPLATE_PREFIX) to match(new RegExp('^[^#]*#template')) broadens the matching criteria, supporting prefixes. This is good for flexibility, but be mindful of lines with special characters or edge cases (e.g., lines with trailing spaces, or lines where # may appear multiple times). Consider testing such edge cases if they exist in user input.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 93262e7 and 64daccb.

⛔ Files ignored due to path filters (1)
  • upcoming-release-notes/4032.md is excluded by !**/*.md
📒 Files selected for processing (3)
  • packages/loot-core/src/server/budget/goal-template.pegjs (2 hunks)
  • packages/loot-core/src/server/budget/template-notes.test.ts (1 hunks)
  • packages/loot-core/src/server/budget/template-notes.ts (1 hunks)
🧰 Additional context used
📓 Learnings (1)
packages/loot-core/src/server/budget/goal-template.pegjs (2)
Learnt from: youngcw
PR: actualbudget/actual#3754
File: packages/loot-core/src/server/budget/goal-template.pegjs:38-43
Timestamp: 2024-11-10T16:45:25.627Z
Learning: In `packages/loot-core/src/server/budget/goal-template.pegjs`, within the `limit` rule, the optional space `_?` is always placed before the `hold` option, ensuring consistency.
Learnt from: youngcw
PR: actualbudget/actual#3754
File: packages/loot-core/src/server/budget/goal-template.pegjs:38-43
Timestamp: 2024-11-10T16:45:25.627Z
Learning: Validations for limit rules, such as checking start date validity and ensuring amounts are positive, are performed during template processing, not in the parser defined in `goal-template.pegjs`.
🔇 Additional comments (3)
packages/loot-core/src/server/budget/goal-template.pegjs (2)

38-42: Return structure enhancements for the limit rule

The new structure for weekly, daily, and monthly limit returns is consistent and includes all necessary properties (amount, hold, start, period). This is beneficial for clarity and uniformity. Ensure relevant unit tests thoroughly cover each branch, including the newly introduced 'weekly' usage.


66-66: Regex-based matching for template rule

Changing the template rule to [ ^#]* '#template' priority: priority? aligns with the updated prefix logic. Be sure to handle edge cases where additional # characters might appear in the line. Also confirm that the presence of potential special characters before #template does not cause unintended matches.

packages/loot-core/src/server/budget/template-notes.test.ts (1)

76-95: Expanded test coverage for prefixed template lines

The new test case ensures that lines containing a prefix before #template are correctly parsed. This is a valuable addition, confirming that recent changes in template-notes.ts and goal-template.pegjs support prefixed inputs. However, consider adding negative or malformed prefix scenarios (e.g., spaces, punctuation, or multiple # markers) to ensure robust coverage.

@@ -63,7 +63,7 @@ schedule = 'schedule'i
full = 'full'i _ {return true}
priority = '-'i number: number {return number}
remainder = 'remainder'i _? weight: positive? { return +weight || 1 }
template = '#template' priority: priority? {return {priority: +priority, directive: 'template'}}
template = [^#]* '#template' priority: priority? {return {priority: +priority, directive: 'template'}}
Copy link
Member

Choose a reason for hiding this comment

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

Could this function be moved into the notes file instead of in the parser?

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