Update to the latest version #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…cePerLength (#668) * Added PoundForcePerFoot and PoundForcePerInch to ForcePerLength * Added PoundForcePerYard to ForcePerLength * Added overloads for multiplication operator to get ForcePerLength from Area * SpecificWeight (and vice-versa)
* Fix for negative feet/inch parsing
* Adding benchmark project * Adding IQuantity tests * Add memory stats * Migrate to netcore to fix build error
* Added RatioChangeRate unit * Fixing issues for RatioChangeRate - Use of DecimalFractionPerSecond as base unit - Correction of the documentation - Adding abbreviation for DecimalFractionPerSecond
* Allowing custom unit conversion functions to be specified * Registering default base->unit and unit->base conversion functions in UnitConverter. Adding test for custom direct conversions * Whitespace consistency * Add some overloads and allowing source/target quantities to be different * Inline initialization and style update for field * PR feedback updates * Regen WRC * Use IQuantity.Value in test case * Rename typeparams, remove empty ctor * Micro optimization of lookup of IQuantity type It was looked up and wrapped N times * UnitConverter: Move static field initialization to static ctor They became a bit unwieldy. Move fields to top of class. * Add typed conversion function for same quantity conversion functions Since this is the most commonly used call path by far, it made sense to handle this case separately. The advantage is that the callback quantity is strongly typed. * Use typed conversions in RegisterDefaultConversions * Header update * Add xmldoc and minor renaming * Add test cases for Type parameters * QuantityParser: Make field readonly * UnitParser: Add test parsing HowMuch custom unit * UnitConverter: Echo quantity when converting to same unit, test custom quantity conversions * Port codegen scripts to C# The only difference is fixing the header of a file. * Regen code
* Added units for Astronomy. * Added Luminosity Quantity
* Run dotCover as part of running tests in build scripts * Upload reports to codecov.io * AppVeyor: Add commented config for enabling remote desktop * Add init scripts to download tooling * Upgrade all nugets * Make test.bat reuse build-functions.psm1 * Move secure envvar to AppVeyor UI, to work with PRs.
Shows the current code coverage %.
* Added SolarRadius unit to Length quantity. * Added SolarTemperature unit to Temperature quantity
* Update README.md * Added link
* UnitMath extension methods (Min, Max, Sum, Average) Added a set of extension methods for some of the most common Math operations, such as Min, Max, Sum and Average (with selector overloads)
* Rename constructor argument 'numericalValue' to 'value' Aligning the name of the constructor argument with the property 'Value' allows MessagePack deserialization of types generated by QuantityGenerator. MessagePack can deserialize immutable types by passing the deserialized values of properties without a setter to an appropriate constructor. * Update generated code
Using VS2019 should hopefully "just work". Clone depth only needs to be big enough to handle all queued builds. Don't build tags, just results in duplicate builds on master branch.
It seems the Windows Runtime Component build fails on missing Windows SDK or something. I don't see anything obvious at: https://www.appveyor.com/docs/windows-images-software/#windows-sdks Need to revisit this. Revert "Fix path to msbuild 16" This reverts commit 0e98fd2.
* Added Millijoule and Ampere hour * Updated A-h converson constants in ElectricCharge.json to match contribution guide and fixed test stubs * Added milli, kilo, and mega A-h prefixes * Updating based on comments from @angularsen on PR #704 * Updating charge units to match library conventions
Pretty much default, except 'help wanted' and 'good first issue' labels to not close.
Auto merge pull requests when ready. Auto rebase or auto merge updates to master into pull requests to keep it up to date. https://github.com/pascalgn/automerge-action
Added benchmarks for UnitSystem methods (UnitSystem.SI)
* Added operator / overload for AreaMomentOfInertia to get Volume when dividing by length * Added test case for AreaMomentOfInertia operator / overload
* Added support for serializing array of units * Added support for deserialization * Fixed build errors in JsonConverter * Added TorquePerLength unit and fixed issue with compatibility project failing on array serialization and deserialization functionality
Found during PR review #712. Addressed separately.
It caused problems with pull requests with error ! [remote rejected] master -> master (refusing to allow an integration to create or update .github/workflows/....
* Added operators for ohm's law * Added overload resistance * current + license
* Updated NuGet packages to latest stable * Updated .NET Core in test projects to match the rest of the solution.
* From YektaMirkan/Units - Added reference pressure property - by gratestas * From YektaMirkan/Units - Added enum of pressure reference - by gratestas * From YektaMirkan/Units - Added pressure wrapper for pressure reference conversion - by gratestas * Broke out tests into individual assertions. Corrected test values in assertions. * Removed line in ReferencePressure.As that was causing sign errors and incorrect vaules and failed test results. * Corrected issues with pressures less than absolute zero * Improved code coverage and corrected exception handling * Renamed unit tests * Sorted unit tests in PressureTests * Updated target framework to latest minor in all projects
* Remove unknown sign from the JSON beginnings Otherways the js JSON parse method returns `SyntaxError: Unexpected token in JSON at position 0` error.
Instead of downloading in AppVeyor during build. This fixes sporadic failed builds due to not being able to fetch this file.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.