plausible/analytics
1
1
Fork 0
mirror of https://github.com/plausible/analytics.git synced 2024-11-26 00:24:44 +03:00
Code Issues Packages Projects Releases Wiki Activity
8a1c6e0913
analytics/priv/sandbox_plans.json

173 lines
4.4 KiB
JSON
Raw Normal View History

Refactor Plausible.Billing.Plans module (#3249) This commit introduces a series of improvements on the Plans module including function renaming, documentation and readability. This is the groundwork for billing plans. There should be no actual changes with this commit, therefore no changes in tests either.
2023-08-09 20:33:59 +03:00
[
{
Refactor Plausible.Billing.Plans module (#3268) This pull request introduces a series of improvements to Plausible.Billing.Plans, including: * Tag the JSON file with the plan version * Rename the JSON field limit to monthly_pageview_limit * Move site_limit function to Billing.Plans * Refactor subscription_interval, allowance and site_limit functions * Remove unused AnalyzePlans task
2023-08-16 19:38:38 +03:00
"kind":"growth",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"generation":1,
Refactor Plausible.Billing.Plans module (#3268) This pull request introduces a series of improvements to Plausible.Billing.Plans, including: * Tag the JSON file with the plan version * Rename the JSON field limit to monthly_pageview_limit * Move site_limit function to Billing.Plans * Refactor subscription_interval, allowance and site_limit functions * Remove unused AnalyzePlans task
2023-08-16 19:38:38 +03:00
"monthly_pageview_limit":10000,
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
"monthly_product_id":"63842",
"yearly_product_id":"63859",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"site_limit":50,
"team_member_limit":"unlimited",
Refactor: Add 'goals' feature to JSON plan files (#3435) * fix text color in dark mode * rename a function * use aliases in quota.ex * rename a function * make Goals a similar feature to others but with a free option * rename a function * mix format
2023-10-18 11:29:13 +03:00
"features":["goals","props","stats_api"]
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
},
{
"kind":"growth",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"generation":2,
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
"monthly_pageview_limit":100000,
"monthly_product_id":"63843",
"yearly_product_id":"63860",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"site_limit":50,
"team_member_limit":"unlimited",
Refactor: Add 'goals' feature to JSON plan files (#3435) * fix text color in dark mode * rename a function * use aliases in quota.ex * rename a function * make Goals a similar feature to others but with a free option * rename a function * mix format
2023-10-18 11:29:13 +03:00
"features":["goals","props","stats_api"]
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
},
{
"kind":"growth",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"generation":3,
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
"monthly_pageview_limit":200000,
"monthly_product_id":"63844",
"yearly_product_id":"63861",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"site_limit":50,
"team_member_limit":"unlimited",
Refactor: Add 'goals' feature to JSON plan files (#3435) * fix text color in dark mode * rename a function * use aliases in quota.ex * rename a function * make Goals a similar feature to others but with a free option * rename a function * mix format
2023-10-18 11:29:13 +03:00
"features":["goals","props","stats_api"]
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
},
{
"kind":"growth",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"generation":4,
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
"monthly_pageview_limit":500000,
"monthly_product_id":"63845",
"yearly_product_id":"63862",
Implement limits for team members (#3305) * Refactor MembershipController.invite_member/2 This commit refactors the controller action used for creating new invitations. It moves the code to Plausible.Sites.invite/4 and replaces `ifs` and `cases` with `with`. * Add team_member_limit to plan definition * Create usage and limits functions for team members * Apply team member limit when inviting new users * Add team members to Usage & Limits section * Change invite function to receive email address instead of %User{} * Wrap invite function in a DB transaction * Remove unnecessary joins from team member usage query * Replace UNION ALL with UNION to remove duplicates
2023-09-04 15:55:07 +03:00
"site_limit":10,
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"team_member_limit":3,
Add data retention to the choose plan page (#3605) * Add data retention field to plans * Display data retention as benefit when choosing plan * Split fields in two module attributes * Remove extra whitespace Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com> --------- Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com>
2023-12-12 14:19:54 +03:00
"features":["goals"],
"data_retention_in_years": 3
Refactor Plausible.Billing.Plans module (#3249) This commit introduces a series of improvements on the Plans module including function renaming, documentation and readability. This is the groundwork for billing plans. There should be no actual changes with this commit, therefore no changes in tests either.
2023-08-09 20:33:59 +03:00
},
{
Refactor Plausible.Billing.Plans module (#3268) This pull request introduces a series of improvements to Plausible.Billing.Plans, including: * Tag the JSON file with the plan version * Rename the JSON field limit to monthly_pageview_limit * Move site_limit function to Billing.Plans * Refactor subscription_interval, allowance and site_limit functions * Remove unused AnalyzePlans task
2023-08-16 19:38:38 +03:00
"kind":"growth",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"generation":4,
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
"monthly_pageview_limit":1000000,
"monthly_product_id":"63846",
"yearly_product_id":"63863",
Implement limits for team members (#3305) * Refactor MembershipController.invite_member/2 This commit refactors the controller action used for creating new invitations. It moves the code to Plausible.Sites.invite/4 and replaces `ifs` and `cases` with `with`. * Add team_member_limit to plan definition * Create usage and limits functions for team members * Apply team member limit when inviting new users * Add team members to Usage & Limits section * Change invite function to receive email address instead of %User{} * Wrap invite function in a DB transaction * Remove unnecessary joins from team member usage query * Replace UNION ALL with UNION to remove duplicates
2023-09-04 15:55:07 +03:00
"site_limit":10,
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"team_member_limit":3,
Add data retention to the choose plan page (#3605) * Add data retention field to plans * Display data retention as benefit when choosing plan * Split fields in two module attributes * Remove extra whitespace Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com> --------- Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com>
2023-12-12 14:19:54 +03:00
"features":["goals"],
"data_retention_in_years": 3
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
},
{
"kind":"growth",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"generation":4,
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
"monthly_pageview_limit":2000000,
"monthly_product_id":"63847",
"yearly_product_id":"63864",
Implement limits for team members (#3305) * Refactor MembershipController.invite_member/2 This commit refactors the controller action used for creating new invitations. It moves the code to Plausible.Sites.invite/4 and replaces `ifs` and `cases` with `with`. * Add team_member_limit to plan definition * Create usage and limits functions for team members * Apply team member limit when inviting new users * Add team members to Usage & Limits section * Change invite function to receive email address instead of %User{} * Wrap invite function in a DB transaction * Remove unnecessary joins from team member usage query * Replace UNION ALL with UNION to remove duplicates
2023-09-04 15:55:07 +03:00
"site_limit":10,
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"team_member_limit":3,
Add data retention to the choose plan page (#3605) * Add data retention field to plans * Display data retention as benefit when choosing plan * Split fields in two module attributes * Remove extra whitespace Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com> --------- Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com>
2023-12-12 14:19:54 +03:00
"features":["goals"],
"data_retention_in_years": 3
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
},
{
"kind":"growth",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"generation":4,
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
"monthly_pageview_limit":5000000,
"monthly_product_id":"63848",
"yearly_product_id":"63865",
Implement limits for team members (#3305) * Refactor MembershipController.invite_member/2 This commit refactors the controller action used for creating new invitations. It moves the code to Plausible.Sites.invite/4 and replaces `ifs` and `cases` with `with`. * Add team_member_limit to plan definition * Create usage and limits functions for team members * Apply team member limit when inviting new users * Add team members to Usage & Limits section * Change invite function to receive email address instead of %User{} * Wrap invite function in a DB transaction * Remove unnecessary joins from team member usage query * Replace UNION ALL with UNION to remove duplicates
2023-09-04 15:55:07 +03:00
"site_limit":10,
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"team_member_limit":3,
Add data retention to the choose plan page (#3605) * Add data retention field to plans * Display data retention as benefit when choosing plan * Split fields in two module attributes * Remove extra whitespace Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com> --------- Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com>
2023-12-12 14:19:54 +03:00
"features":["goals"],
"data_retention_in_years": 3
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
},
{
"kind":"growth",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"generation":4,
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
"monthly_pageview_limit":10000000,
"monthly_product_id":"63849",
"yearly_product_id":"63866",
Implement limits for team members (#3305) * Refactor MembershipController.invite_member/2 This commit refactors the controller action used for creating new invitations. It moves the code to Plausible.Sites.invite/4 and replaces `ifs` and `cases` with `with`. * Add team_member_limit to plan definition * Create usage and limits functions for team members * Apply team member limit when inviting new users * Add team members to Usage & Limits section * Change invite function to receive email address instead of %User{} * Wrap invite function in a DB transaction * Remove unnecessary joins from team member usage query * Replace UNION ALL with UNION to remove duplicates
2023-09-04 15:55:07 +03:00
"site_limit":10,
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"team_member_limit":3,
Add data retention to the choose plan page (#3605) * Add data retention field to plans * Display data retention as benefit when choosing plan * Split fields in two module attributes * Remove extra whitespace Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com> --------- Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com>
2023-12-12 14:19:54 +03:00
"features":["goals"],
"data_retention_in_years": 3
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
},
{
"kind":"business",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"generation":3,
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
"monthly_pageview_limit":10000,
"monthly_product_id":"63850",
"yearly_product_id":"63867",
Implement limits for team members (#3305) * Refactor MembershipController.invite_member/2 This commit refactors the controller action used for creating new invitations. It moves the code to Plausible.Sites.invite/4 and replaces `ifs` and `cases` with `with`. * Add team_member_limit to plan definition * Create usage and limits functions for team members * Apply team member limit when inviting new users * Add team members to Usage & Limits section * Change invite function to receive email address instead of %User{} * Wrap invite function in a DB transaction * Remove unnecessary joins from team member usage query * Replace UNION ALL with UNION to remove duplicates
2023-09-04 15:55:07 +03:00
"site_limit":50,
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"team_member_limit":"unlimited",
Refactor: Add 'goals' feature to JSON plan files (#3435) * fix text color in dark mode * rename a function * use aliases in quota.ex * rename a function * make Goals a similar feature to others but with a free option * rename a function * mix format
2023-10-18 11:29:13 +03:00
"features":["goals","props", "revenue_goals", "funnels","stats_api"]
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
},
{
"kind":"business",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"generation":3,
Refactor Plausible.Billing.Plans module (#3268) This pull request introduces a series of improvements to Plausible.Billing.Plans, including: * Tag the JSON file with the plan version * Rename the JSON field limit to monthly_pageview_limit * Move site_limit function to Billing.Plans * Refactor subscription_interval, allowance and site_limit functions * Remove unused AnalyzePlans task
2023-08-16 19:38:38 +03:00
"monthly_pageview_limit":100000,
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
"monthly_product_id":"63851",
"yearly_product_id":"63868",
Implement limits for team members (#3305) * Refactor MembershipController.invite_member/2 This commit refactors the controller action used for creating new invitations. It moves the code to Plausible.Sites.invite/4 and replaces `ifs` and `cases` with `with`. * Add team_member_limit to plan definition * Create usage and limits functions for team members * Apply team member limit when inviting new users * Add team members to Usage & Limits section * Change invite function to receive email address instead of %User{} * Wrap invite function in a DB transaction * Remove unnecessary joins from team member usage query * Replace UNION ALL with UNION to remove duplicates
2023-09-04 15:55:07 +03:00
"site_limit":50,
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"team_member_limit":"unlimited",
Refactor: Add 'goals' feature to JSON plan files (#3435) * fix text color in dark mode * rename a function * use aliases in quota.ex * rename a function * make Goals a similar feature to others but with a free option * rename a function * mix format
2023-10-18 11:29:13 +03:00
"features":["goals","props", "revenue_goals", "funnels","stats_api"]
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
},
{
"kind":"business",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"generation":3,
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
"monthly_pageview_limit":200000,
"monthly_product_id":"63852",
"yearly_product_id":"63869",
Implement limits for team members (#3305) * Refactor MembershipController.invite_member/2 This commit refactors the controller action used for creating new invitations. It moves the code to Plausible.Sites.invite/4 and replaces `ifs` and `cases` with `with`. * Add team_member_limit to plan definition * Create usage and limits functions for team members * Apply team member limit when inviting new users * Add team members to Usage & Limits section * Change invite function to receive email address instead of %User{} * Wrap invite function in a DB transaction * Remove unnecessary joins from team member usage query * Replace UNION ALL with UNION to remove duplicates
2023-09-04 15:55:07 +03:00
"site_limit":50,
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"team_member_limit":"unlimited",
Refactor: Add 'goals' feature to JSON plan files (#3435) * fix text color in dark mode * rename a function * use aliases in quota.ex * rename a function * make Goals a similar feature to others but with a free option * rename a function * mix format
2023-10-18 11:29:13 +03:00
"features":["goals","props", "revenue_goals", "funnels","stats_api"]
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
},
{
"kind":"business",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"generation":4,
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
"monthly_pageview_limit":500000,
"monthly_product_id":"63853",
"yearly_product_id":"63870",
Implement limits for team members (#3305) * Refactor MembershipController.invite_member/2 This commit refactors the controller action used for creating new invitations. It moves the code to Plausible.Sites.invite/4 and replaces `ifs` and `cases` with `with`. * Add team_member_limit to plan definition * Create usage and limits functions for team members * Apply team member limit when inviting new users * Add team members to Usage & Limits section * Change invite function to receive email address instead of %User{} * Wrap invite function in a DB transaction * Remove unnecessary joins from team member usage query * Replace UNION ALL with UNION to remove duplicates
2023-09-04 15:55:07 +03:00
"site_limit":50,
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"team_member_limit":10,
Add data retention to the choose plan page (#3605) * Add data retention field to plans * Display data retention as benefit when choosing plan * Split fields in two module attributes * Remove extra whitespace Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com> --------- Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com>
2023-12-12 14:19:54 +03:00
"features":["goals","props", "revenue_goals", "funnels","stats_api"],
"data_retention_in_years": 5
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
},
{
"kind":"business",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"generation":4,
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
"monthly_pageview_limit":1000000,
"monthly_product_id":"63854",
"yearly_product_id":"63871",
Implement limits for team members (#3305) * Refactor MembershipController.invite_member/2 This commit refactors the controller action used for creating new invitations. It moves the code to Plausible.Sites.invite/4 and replaces `ifs` and `cases` with `with`. * Add team_member_limit to plan definition * Create usage and limits functions for team members * Apply team member limit when inviting new users * Add team members to Usage & Limits section * Change invite function to receive email address instead of %User{} * Wrap invite function in a DB transaction * Remove unnecessary joins from team member usage query * Replace UNION ALL with UNION to remove duplicates
2023-09-04 15:55:07 +03:00
"site_limit":50,
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"team_member_limit":10,
Add data retention to the choose plan page (#3605) * Add data retention field to plans * Display data retention as benefit when choosing plan * Split fields in two module attributes * Remove extra whitespace Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com> --------- Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com>
2023-12-12 14:19:54 +03:00
"features":["goals","props", "revenue_goals", "funnels","stats_api"],
"data_retention_in_years": 5
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
},
{
"kind":"business",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"generation":4,
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
"monthly_pageview_limit":2000000,
"monthly_product_id":"63855",
"yearly_product_id":"63872",
Implement limits for team members (#3305) * Refactor MembershipController.invite_member/2 This commit refactors the controller action used for creating new invitations. It moves the code to Plausible.Sites.invite/4 and replaces `ifs` and `cases` with `with`. * Add team_member_limit to plan definition * Create usage and limits functions for team members * Apply team member limit when inviting new users * Add team members to Usage & Limits section * Change invite function to receive email address instead of %User{} * Wrap invite function in a DB transaction * Remove unnecessary joins from team member usage query * Replace UNION ALL with UNION to remove duplicates
2023-09-04 15:55:07 +03:00
"site_limit":50,
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"team_member_limit":10,
Add data retention to the choose plan page (#3605) * Add data retention field to plans * Display data retention as benefit when choosing plan * Split fields in two module attributes * Remove extra whitespace Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com> --------- Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com>
2023-12-12 14:19:54 +03:00
"features":["goals","props", "revenue_goals", "funnels","stats_api"],
"data_retention_in_years": 5
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
},
{
"kind":"business",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"generation":4,
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
"monthly_pageview_limit":5000000,
"monthly_product_id":"63856",
"yearly_product_id":"63873",
Implement limits for team members (#3305) * Refactor MembershipController.invite_member/2 This commit refactors the controller action used for creating new invitations. It moves the code to Plausible.Sites.invite/4 and replaces `ifs` and `cases` with `with`. * Add team_member_limit to plan definition * Create usage and limits functions for team members * Apply team member limit when inviting new users * Add team members to Usage & Limits section * Change invite function to receive email address instead of %User{} * Wrap invite function in a DB transaction * Remove unnecessary joins from team member usage query * Replace UNION ALL with UNION to remove duplicates
2023-09-04 15:55:07 +03:00
"site_limit":50,
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"team_member_limit":10,
Add data retention to the choose plan page (#3605) * Add data retention field to plans * Display data retention as benefit when choosing plan * Split fields in two module attributes * Remove extra whitespace Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com> --------- Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com>
2023-12-12 14:19:54 +03:00
"features":["goals","props", "revenue_goals", "funnels","stats_api"],
"data_retention_in_years": 5
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
},
{
"kind":"business",
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"generation":4,
Create new sandbox plans based on V4 (#3308)
2023-08-30 17:41:55 +03:00
"monthly_pageview_limit":10000000,
"monthly_product_id":"63857",
"yearly_product_id":"63874",
Implement limits for team members (#3305) * Refactor MembershipController.invite_member/2 This commit refactors the controller action used for creating new invitations. It moves the code to Plausible.Sites.invite/4 and replaces `ifs` and `cases` with `with`. * Add team_member_limit to plan definition * Create usage and limits functions for team members * Apply team member limit when inviting new users * Add team members to Usage & Limits section * Change invite function to receive email address instead of %User{} * Wrap invite function in a DB transaction * Remove unnecessary joins from team member usage query * Replace UNION ALL with UNION to remove duplicates
2023-09-04 15:55:07 +03:00
"site_limit":50,
List plan benefits on the new upgrade page (#3444) * change team member limits for new v4 plans * duplicate business plans with unlimited team members We need to do this because we want grandfathered users to have unlimited team members on business plans as well. Otherwise we'd have to build overrides on the subscription level when checking the limit. * refactor generating plan structs * move Plan module into a separate file * remove not needed conditions * add generation field to plans * sync the sanbox plan limits and features with plan generations * implement displaying plan benefits * add grandfathering notice * plug in the real v3 business plan IDs * optimize N/A text color for darkmode * use String.to_existing_atom instead Co-authored-by: Vini Brasil <vini@hey.com> * Remove the unnecessary part of a comment Co-authored-by: Vini Brasil <vini@hey.com> * make the Plan.new function simpler * use exlamation marks --------- Co-authored-by: Vini Brasil <vini@hey.com>
2023-10-23 19:42:00 +03:00
"team_member_limit":10,
Add data retention to the choose plan page (#3605) * Add data retention field to plans * Display data retention as benefit when choosing plan * Split fields in two module attributes * Remove extra whitespace Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com> --------- Co-authored-by: Adrian Gruntkowski <adrian.gruntkowski@gmail.com>
2023-12-12 14:19:54 +03:00
"features":["goals","props", "revenue_goals", "funnels","stats_api"],
"data_retention_in_years": 5
Refactor Plausible.Billing.Plans module (#3249) This commit introduces a series of improvements on the Plans module including function renaming, documentation and readability. This is the groundwork for billing plans. There should be no actual changes with this commit, therefore no changes in tests either.
2023-08-09 20:33:59 +03:00
}
]
Reference in New Issue Copy Permalink