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

[core] Config V2 & deprecate unused code #218

Open
wants to merge 2 commits into
base: ml/new-payments-design
Choose a base branch
from

Conversation

manolisliolios
Copy link
Collaborator

@manolisliolios manolisliolios commented Nov 29, 2024

I did a minor restructure of the codebase to deprecate what's not needed.

That (for now) includes:

  1. update_image.move: We have proceeded with a different design overall.
  2. config.move: I created a CoreConfig which is more flexible for future updates, and covers all our current needs. (please see todo point for discussion).
  3. auction.move: I kept the auction codebase (and actually ported it to our new config), but decided to move it to the deprecated folder to remove confusion. This system is no longer usable.

Additional changes:

  1. Introduce payments_version in the configuration: This allows us to prevent PaymentIntent from being finalized if it does not match the "configured" version from admin.

Follow-ups:

I also wanna re-write controller.move to do whatever direct_setup package does. There's no reason for us not to offer the basic functionality from our core package, now that we know that the basics will (most likely) never change. We can always deauthorize it too so thats also good news 😄

Tests fail because of renewal, register and discount_house packages. I leave them here on purpose to avoid merge conflicts down the path. Their rewrite is coming up too.

Copy link

changeset-bot bot commented Nov 29, 2024

⚠️ No Changeset found

Latest commit: 6b2142f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Nov 29, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
suins-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 29, 2024 2:37pm

@@ -15,7 +15,7 @@
/// useful for system-level discounts, or user-specific discounts.
///
/// TODO: Consider re-using `RequestData` inside the `Receipt`.
/// TODO: Add settings for max year of renewals / max duration of registration here?
/// TODO: Add settings for max year of renewals / max duration of registration here?
Copy link
Contributor

Choose a reason for hiding this comment

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

I like this but let's include in a separate PR

@manolisliolios manolisliolios changed the title Config V2 & deprecate unused code [core] Config V2 & deprecate unused code Dec 2, 2024
public_key: vector<u8>,
/// Minimum length of the label part of the domain. This is different from
/// the base `domain` checks. This is our minimum acceptable length (for sales).
/// TODO: Shoudl we consider removing this? Our range is [1,63] by design, and
Copy link
Contributor

Choose a reason for hiding this comment

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

We can keep this as backup or in case we redesign in the future

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.

2 participants