You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are newer and better pricing models in development, but existing pricing code is currently spread across several core plugins. If a custom pricing plugin is added, it will have data alongside the current pricing fields, which would not be used. This would be confusing.
Work
Move all code and schemas related to product and catalog pricing into an included plugin, which should be removable. The goal is to be able to remove it and swap in a different custom pricing plugin, with everything still working.
The text was updated successfully, but these errors were encountered:
This is mostly done by #5014, but we should do an audit to be sure everything is moved to the plugin. I think we skipped a few things due to time constraints.
Background
There are newer and better pricing models in development, but existing pricing code is currently spread across several core plugins. If a custom pricing plugin is added, it will have data alongside the current pricing fields, which would not be used. This would be confusing.
Work
Move all code and schemas related to product and catalog pricing into an
included
plugin, which should be removable. The goal is to be able to remove it and swap in a different custom pricing plugin, with everything still working.The text was updated successfully, but these errors were encountered: