Describe your bug or feature request.

As of Drupal 10.2.0, new Plugin implementations should use PHP attributes. Core already migrated field formatters, field types and field widgets to attributes (See https://www.drupal.org/docs/drupal-apis/plugin-api/attribute-based-plugins for more information).

We should support that from Commerce 3, which now requires D10.3 minimum.
We need to define new attributes for PaymentGateway, PaymentMethodType, PaymentType, TaxType, PromotionOffer etc...

We should still support annotations but eventually drop annotation support at the end of the Commerce 3 cycle so Commerce 4 can drop support and work on Drupal 12.

Issue fork commerce-3463795

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

jsacksick created an issue. See original summary.

jsacksick opened merge request !282

jsacksick’s picture

jsacksick commented

I started by defining TaxType and TaxNumberType attributes... But now I'm wondering... Perhaps it makes sense to prefix our attributes (just like our annotations, by Commerce, to be consistent with what was done for annotations...)

So TaxType would become CommerceTaxType for example.

  • jsacksick committed 8c977176 on 3.0.x 
    Issue #3463795 by jsacksick: Convert CheckoutFlow, CheckoutPane,...
jsacksick’s picture

jsacksick commented
Title: Implement support for Attribute-based plugins » Convert CheckoutFlow, CheckoutPane, NumberPattern, PaymentGateway, PaymentMethodType, PaymentType, TaxType, TaxNumberType to attributes.
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.