Skip to content

fix(payments): connector config compatibility #1754

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.

Sign up for GitHub

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

Jump to bottom
Merged
laouji merged 3 commits into from
Mar 25, 2025
Merged

fix(payments): connector config compatibility #1754

laouji merged 3 commits into from
Mar 25, 2025

Conversation

@laouji
Copy link

@laouji laouji commented Mar 21, 2025 •
edited
Loading

Fixes: PMNT-68

Relates to: formancehq/fctl#37

Additionally:

in v2 pollingPeriod is internally a struct, but it has a special Marshal function that converts it into a string
because we unmarshal and marshal again to inject the provider string needed for the fctl patch to work, we also need to patch polling period to avoid this error:

could not unmarshal `{"apiKey":"REDACTED","apiSecret":"REDACTED","endpoint":"https://api-sandbox.modulrfinance.com/api-sandbox-token/","name":"modulr-0325-1347","pageSize":100,"pollingPeriod":{"duration":120000000000},"provider":"Modulr"}` into expected (Provider == Modulr) type ModulrConfig within ConnectorConfig: json: cannot unmarshal object into Go value of type string
  ERROR   json: cannot unmarshal object into Go value of type string

therefore this PR also changes "pollingPeriod":{"duration":120000000000} to "pollingPeriod":"2m0s" if polling period is a struct

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 21, 2025 •
edited
Loading

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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.

@laouji laouji marked this pull request as ready for review March 25, 2025 16:15
@laouji laouji requested a review from a team as a code owner March 25, 2025 16:15
@laouji laouji merged commit 67577dd into releases/v2.0.0 Mar 25, 2025
12 checks passed
@laouji laouji deleted the fix/payments-connector-config-compatibility branch March 25, 2025 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@paul-nicolas paul-nicolas paul-nicolas approved these changes

Assignees

No one assigned

Labels

components/payments

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@laouji @paul-nicolas