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

Fix Hype Bank sync (HYPE_HYEEIT22) #511

Merged
merged 3 commits into from
Nov 28, 2024
Merged

Conversation

guglicap
Copy link
Contributor

@guglicap guglicap commented Nov 28, 2024

Hello, as title says, Hype Bank sync is currently broken.
This is because this bank is one of the limited history ones, but the wrong institution ID is set in the BANKS_WITH_LIMITED_HISTORY array.
This fixes #462 by replacing the wrong id with the correct one.

@actual-github-bot actual-github-bot bot changed the title Fix Hype Bank sync (HYPE_HYEEIT22) [WIP] Fix Hype Bank sync (HYPE_HYEEIT22) Nov 28, 2024
@guglicap guglicap changed the title [WIP] Fix Hype Bank sync (HYPE_HYEEIT22) Fix Hype Bank sync (HYPE_HYEEIT22) Nov 28, 2024
Copy link
Contributor

coderabbitai bot commented Nov 28, 2024

Walkthrough

The pull request modifies the BANKS_WITH_LIMITED_HISTORY constant in the src/app-gocardless/bank-factory.js file. The specific change involves updating the bank identifier from 'HYPE_HYEEIT2' to 'HYPE_HYEEIT22', which appears to correct a typo or inconsistency. This adjustment impacts the list of banks recognized as having limited transaction history, ensuring that the correct identifier is used. No other parts of the file, including imports and logic for finding banks based on institution IDs, have been altered.

Possibly related issues

Possibly related PRs

Suggested labels

:sparkles: Merged

Suggested reviewers

  • jfdoming

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 (1)
src/app-gocardless/bank-factory.js (1)

Missing Hype Bank implementation

The bank factory includes institution IDs 'HYPE_BUSINESS_HYEEIT22' and 'HYPE_HYEEIT22' in the BANKS_WITH_LIMITED_HISTORY array, but there is no corresponding bank implementation file in the codebase. This means these transactions will fall back to the IntegrationBank implementation, which might not provide bank-specific handling if required.

  • Missing implementation file for Hype Bank in src/app-gocardless/banks/
  • Institution IDs 'HYPE_BUSINESS_HYEEIT22' and 'HYPE_HYEEIT22' are not mapped to any specific bank implementation
🔗 Analysis chain

Line range hint 52-54: Verify Hype Bank implementation exists with correct institution ID.

Since the bank factory uses institution IDs to find the correct bank implementation, we should ensure the Hype Bank implementation exists and includes this ID.

Let's verify the bank implementation:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for Hype Bank implementation file
fd -t f "hype" src/app-gocardless/banks/

# If found, verify the institution ID is correctly defined
ast-grep --pattern 'institutionIds = [$$$"HYPE_HYEEIT22"$$$]'

Length of output: 104


Script:

#!/bin/bash
# Let's try a broader search for any files containing "hype" case-insensitive
rg -i "hype" src/app-gocardless/ -A 5 -B 5

# Also search for any bank implementation files
fd -t f "bank" src/app-gocardless/banks/

# Let's also check the bank factory to see the context of bank implementations
cat src/app-gocardless/bank-factory.js

Length of output: 5195


Script:

#!/bin/bash
# Let's search for a Hype bank implementation file with different naming patterns
fd -t f "(hype|hyee)" src/app-gocardless/banks/

# Let's also check if there might be a dots bank implementation since we see DOTS_HYEEIT22
fd -t f "dots" src/app-gocardless/banks/

# Let's also look for any file containing HYEEIT22 which is the bank identifier
rg "HYEEIT22" src/app-gocardless/banks/ -l

Length of output: 133

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 8506b87 and 8c95fee.

⛔ Files ignored due to path filters (1)
  • upcoming-release-notes/511.md is excluded by !**/*.md
📒 Files selected for processing (1)
  • src/app-gocardless/bank-factory.js (1 hunks)
🔇 Additional comments (1)
src/app-gocardless/bank-factory.js (1)

83-83: LGTM! The institution ID update aligns with other Hype-related entries.

The change from 'HYPE_HYEEIT2' to 'HYPE_HYEEIT22' is consistent with other Hype-related entries in the array that use the same 'HYEEIT22' suffix (e.g., HYPE_BUSINESS_HYEEIT22, DOTS_HYEEIT22, TIM_HYEEIT22).

Let's verify this institution ID is properly referenced in bank implementations:

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!

@matt-fidd matt-fidd merged commit 4842111 into actualbudget:master Nov 28, 2024
8 checks passed
meonkeys added a commit to meonkeys/actual-server that referenced this pull request Dec 2, 2024
* master:
  Fix Hype Bank sync (`HYPE_HYEEIT22`)  (actualbudget#511)
  🐛 Fix existing sessions when using the latest version with Openid (actualbudget#507)
meonkeys pushed a commit to meonkeys/actual-server that referenced this pull request Dec 2, 2024
* fix: wrong institution_id for HYPE_HYEEIT22 in `BANKS_WITH_LIMITED_HISTORY` array

* added upcoming-release-note

* fixed author name in release note
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]: Extended history of special banks sync with gocardless
2 participants