XP One nuget per quantity #1181
Draft
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.
Related to #372, #1180
Experiment with splitting up UnitsNet nuget into:
This is already done for UnitsNet.nanoFramework nugets:
https://www.nuget.org/packages?q=unitsnet.nanoframework
We might also provide meta nuget packages that bring in multiple nugets in a single package:
Benefits
UnitsNet.dll
is ~2MB as of 2023-01-07.Problems
QuantityType
enum must be replaced by strings and usingQuantityInfo
insteadUnitSystem
andBaseUnits
rely on the 7 SI quantities Length, Mass, etc.Speed = Length / Duration
andMass.FromGravitationalForce(Force f)
. We might be able to provide this with meta nuget packages that bring in the most common quantities and arithmetic/conversions between them.Design proposal
QuantityInfo
to fully describe a quantity, instead of relying on generated code for known quantities spread over various types.UnitAbbreviationsCache.LoadGeneratedAbbreviations()
based on generated code.Acceleration.RegisterDefaultConversions
and similar for other quantities.