Internal cleanup & minor changes. Fixed README & (package/README) logo issues

Full Changelog: 3.0.6...3.0.7

What's Changed

• Fixed an off by 1 issue related to maxmium GeneratorId. by @Throwy in #62

New Contributors

• @Throwy made their first contribution in #62

Full Changelog: 3.0.5...3.0.6

This is a maintenance release. No changes in packages. From now on we use GitHub actions to build and publish Nuget packages.

Minor internal refactoring.

• ID is now a record
• Fixed bounds check where when the GeneratorId was 31 bits the constructor would throw on any generator id.

Minor internal refactoring. Also an Idgen.DependencyInjection package is now available.

This release contains a few (minor) breaking changes. Generated 2.x ID's are still compatible with 3.x ID's.

• Most of the constructor overloads for the IdGenerator have been replaced with a single constructor which accepts IdGeneratorOptions that contains the ITimeSource, IdStructure and SequenceOverflowStrategy.
• The MaskConfig class is now more appropriately named IdStructure since it describes the structure of the generated ID's.
• The UseSpinWait property has moved to the IdGeneratorOptions and is now an enum of type SequenceOverflowStrategy instead of a boolean value. Note that this property has also been renamed in the config file (from useSpinWait to sequenceOverflowStrategy) and is no longer a boolean but requires one of the values from SequenceOverflowStrategy.
• ID is now Id (only used as return value by the FromId(...) method)

The IdGenerator now offers a spinwaiting strategy when a sequenceoverflow occurs instead of throwing a SequenceOverflowException. This will spinwait until the next tick and then return a new Id. New constructoroverloads have been added to be able to set this property at construction time. Also the configuration package supports this new option with a useSpinWait attribute on the idGenerator element.

Fix concurrency issue (see PR #23). Upped version.

Changes:

• Added TryCreate() method (see #21)
• Fix bug where different instances didn't share the same offset (see #20)