Skip to content

Conversation

annvelents
Copy link
Contributor

Context

As fee now can be related to a fixed_charge, items will be charge fee's addon, so a lot of item-related methods should be updated

Description

  • added new fee_type
  • updated item methods on fee
  • updated tests

@annvelents annvelents force-pushed the feat/fixed_charges-1/update-fee-model branch from b5c4cae to 9ddc807 Compare July 21, 2025 08:52
@annvelents annvelents force-pushed the feat/fixed_charges-1/migration-update-fee branch from 846895f to e845108 Compare July 30, 2025 20:08
@annvelents annvelents force-pushed the feat/fixed_charges-1/update-fee-model branch from 9ddc807 to e8ddad9 Compare July 30, 2025 20:23
Copy link
Contributor

@ancorcruz ancorcruz left a comment

Choose a reason for hiding this comment

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

LGTM!

@annvelents annvelents force-pushed the feat/fixed_charges-1/migration-update-fee branch from 5e4d6e0 to 2effb40 Compare August 1, 2025 11:39
## Context

As part of work on fixed charges, subscription will have many
fixed_charges through plan and also many add_ons through fixed charges

## Description

- updated subscription model
- updated subscription model spec
Base automatically changed from feat/fixed_charges-1/migration-update-fee to main August 5, 2025 07:36
@ancorcruz ancorcruz merged commit 6dd97f7 into main Aug 5, 2025
14 checks passed
@ancorcruz ancorcruz deleted the feat/fixed_charges-1/update-fee-model branch August 5, 2025 09:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants