Jump to content

Recommended Posts

Posted

I see that the "prorate" parameter is marked as deprecated >4.0+.  What's the intended future functionality?

I'd imagine that it's simply get rid of the "if" block here and always do proration?  That will be pretty inconvenient as there's many times when editing a service that you don't want to prorate.

There's no code or anything to imply what the intended future functionality is so I'm hoping for some answers here.

Posted

The intent is to perform proration separately from a service edit, such as apart of a pricing presenter (which is what we had done in some places, like queued service changes, in v4.0), and overall decrease the number of separate actions that a service edit performs.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...