cosmos-stack / cosmos-standard Goto Github PK

Take out "Disposable" alone to become an independent project. #44

Add Optional extensions

• Maybe
• Either
• Some
• None

For the following reasons, we will start with Cosmos.Standard 0.1.5, switch the entire TargetFramework to .NET Core 3.1, and no longer consider .NET Framework, .NET Core 1.x/2.x/3.0,. NET Standard provides support:

• .NET 5 will completely replace .NET Framework and .NET Core;
• .NET 5 played down the existence of .NET Standard;
• The complex target framework is not conducive to the development (rewriting) of Cosmos.One;
• The existing version of the Cosmosloops ecosystem has not been accepted by most people, so there is no historical burden;
• Easy to test;
• Other reasons.

Considering that the Loongson team is adapting Mips64 for .NET Core 3.1 (and will not know whether they will also adapt for .NET 5 in a short time), so when .NET 5 is released, Cosmos.Standard will simultaneously Supports .NET Core 3.1 and .NET 5.

cosmos-loops/Home#1

According to #44, merge "Collections" extensions of Cosmos.Extensions library and "Collections" extensions of Cosmos.Extensions.Collections into the core library.

At the same time complete the corresponding unit test.

Preparation for version 0.1.5: Refactoring Standard Library

According to #44, merge "CharMatcher" of Cosmos.Extensions library into the core library.

At the same time complete the corresponding unit test.

为 Cosmos.Extensions.Preconditions 增加验证拦截器

According to #44, merge "Splitter" of Cosmos.Extensions library into the core library.

At the same time complete the corresponding unit test.

Add FluentException apis

Reference to:
https://github.com/toeb/fluentexceptions

According to #44, merge "Optionals" extensions of Cosmos.Extensions library into the core library.

At the same time complete the corresponding unit test.

By adding HashCode32, HashCode64, HashCode128, HashCode256, HashCode512 and HashCode1024, the processing capability of HashCode is enhanced.

• Automatic adaptation of high and low positions
• Convert to hexadecimal string
  • Provide: AsHexString() and AsHexString(bool uppercase) methods
• Convert to a binary string (and complete 0, optional)
  • Provide: AsBinString() and AsBinString(bool completeZero) methods
• Hexadecimal strings can be parsed as HashCode-NN
  • Provide: Parse, TryParse, ParseLoosely and TryParseLoosely methods
  • In loose mode, strings with insufficient length can also be easily converted to HashCode-NN
  • In strict mode, only strings that strictly meet the requirements can be converted successfully.
• Provides methods to convert to Byte[] and BitArray.
• Also provides a method to convert to Base64.

Add Promise extensions by C-Sharp-Promise

According to #44, merge "Try" of Cosmos.Extensions library into the core library.

At the same time complete the corresponding unit test.

According to #44, merge "RegexUtils" of Cosmos.Extensions library into the core library.

At the same time complete the corresponding unit test.

重构 Cosmos.Serialization 体系

Integrate the default mapping mechanism in the Conversions library.

According to #44, merge "IdUtils" of Cosmos.Extensions library into the core library.

At the same time complete the corresponding unit test.

According to #44, merge "Joiner" of Cosmos.Extensions library into the core library.

At the same time complete the corresponding unit test.

The Hex utility can easily switch the hexadecimal value between string and byte[].

Usage:

Kanban: https://trello.com/c/RaKQFBg1
Document：Chinese Version | English Version

• Enhanced Try.Create<>() overload.
• Add Try.Invoke<>(Action<>) overload.
• Add TryAction wrapper.
• Add TryInvoke extension methods for Action and TryFuncInvoke extension methods for Func
• Add Future Create feature
• Add Future Invoking feature
• Add TryInvokingException

According to #44, merge "Conversions" of Cosmos.Extensions library into the core library.

• Conversions
• Conversions extensions
• CastTo extensions
• Safe&null extensions

At the same time complete the corresponding unit test.

To optimize and streamline Cosmos.Standard's core library design, it was decided to merge Cosmos.Core and Cosmos.Extensions.

This adjustment helps to clarify the logical relationship between auxiliary methods and extension methods, and adjust the accessibility of some methods to achieve "as reasonable a design as possible".