Remove string field type from price field

[josee-sabourin]

What problem does your proposal solve? Please begin with the relevant issue number. If there is no existing issue, please also describe alternative solutions you have considered.

price field in system_pricing_plans.json allowed for both string and non-negative float field types.

What is the proposal?

price will now only allow for non-negative float field types.

Is this a breaking change?

• Yes
• No
• Unsure

Which files are affected by this change?

• system_pricing_plans.json

[mplsmitch]

I hereby call a vote on this proposal. Voting will be open for 10 full calendar days until 11:59PM UTC on December 9, 2021.

Please vote for or against the proposal, and include the organization for which you are voting in your comment.

Please note if you can commit to implementing the proposal.

[kanagy]

+1 from Google Maps

[richtaylor-ito]

+1 from Ito World.

[cmonagle]

+1 from Transit

[testower]

Entur supports this proposal

[nbdh]

+1 from nextbike

[heidiguenin]

Voting on this PR closes in 2 calendar days. Please vote for or against the proposal, and include the organization for which you are voting in your comment. Please note if you can commit to implementing the proposal.

[ncancelliere]

+1 from Spin.

[heidiguenin]

This vote has now closed, and it passes!

Votes in favor:
Google Maps (consumer)
Ito World (producer)
Transit (consumer)
Entur (consumer)
nextbike (producer)
Spin (producer)

There were no votes against.
Thank you to everyone who took the time to review and to vote on this!

We will tag and merge this into v3.0-RC2 in the coming weeks.