routerrpc: fix fee limit validation and calculation#9671
routerrpc: fix fee limit validation and calculation#9671asmit27rai wants to merge 1 commit intolightningnetwork:masterfrom
Conversation
This commit: 1. Makes fixed and fixed_msat fee limits mutually exclusive 2. Properly handles percentage-based fee limits 3. Adds validation for conflicting fee limit fields 4. Maintains backward compatibility 5. Adds helper functions for fee limit calculation Fixes issue with inconsistent fee limit behavior where: - Fixed and fixed_msat could be set simultaneously without error - Percentage fee limits were not properly respected - No clear validation of fee limit fields
|
Important Review skippedAuto reviews are limited to specific labels. 🏷️ Labels to auto review (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
@saubyk @AndySchroder |
|
Hi @asmit27rai please go through the guidelines published for new contributors: New contributors are expected to contribute to code review first, before expecting review on their prs. Thanks. |
Change Description
This PR fixes inconsistent behavior in fee limit validation and calculation for both
SendPaymentandSendPaymentV2RPC calls. The changes:fixedandfixed_msatfee limits mutually exclusive (error if both set)Fixes: #7832