This repository has been archived by the owner on Aug 16, 2021. It is now read-only.
[3.0.8.0] API models shouldn't use string to hold Value amounts #4087
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://stratisplatformuk.visualstudio.com/StratisBitcoinFullNode/_workitems/edit/3904/
Re: "... currently MoneyFormatAttribute is causing us problems because Money.TryParse doesn't understand scientific notation ..."
I suggest that we improve consistency without changing the APIs in any way. The root issue seems to be that we (or external callers) are not always using the
ToString
method of theMoney
class to convert money values to strings. As a result we end up with a string that is not guaranteed to be parsable by theMoney
class.Changes in this PR:
decimal.ToString
. UseMoney.ToString
instead.Money.TryParse
(for external callers).