GEMD v0.14.1 is released!

What's new

• Better scope control for our Cake demo makes it easier to have a few different copies for different people to experiment with.

Fixes

• Some misbehavior is CaseInsensitiveDicts around key deletion has been fixed, as well as bringing the whole file in line in our contribution guidelines.

GEMD v0.13.2 is released!

Fixes

• This release includes augmented documentation and demonstration data updates.

GEMD v0.13.0 is released!

What's New

• ValidList's can now be passed a function to call on all arguments, making it possible to mutate arguments before assignment or perform more complex validation logic.
• Using the new functionality, all attribute lists in Object Templates can now modify incoming arguments. This means you can assign an AttributeTemplate to the properties, conditions, or parameters` fields and the library will convert it into a tuple with default/pass-through bounds.

Fixes

• With the move to v0.13.0, several deprecated methods have been removed. This includes direct assignment of name and labels to Ingredient Runs and the initial serialization approaches (gemd.client).

GEMD v0.12.1 is released!

This release corrects issues in the previous release.

Bugfixes

• name and labels fields on Ingredient Runs could be stale following some orders of operations. This corrects this by directly pulling the data in from an associated Ingredient Spec where possible.

v0.12.0 is released!

What's New

• Following from our shift in best practices (as described in the docs), we are migrating Object constructors to conform. Specifically, we are removing the option to use positional arguments.
• The name and labels arguments to the IngredientRun constructor have been deprecated for quite some time, and so those arguments have been removed.

Fixes

• The setting of name and labels fields within IngredientRun objects has been deprecated for some time, but there were no explicit warnings being emitted. To help people migrate code, appropriate warnings have been added to the setters for those fields.

v0.11.1 is released!

Fixes

• The cake demonstration code had UIDs that collided in a case-insensitive way. This has been corrected, and the tests augmented to include that scenario.
• In JSON serialization for python < 3.6, there appear to be some cases where ints are serialized as floats, which in turn caused type errors on ingest. NominalInteger and UniformInteger are now float tolerant so long as the value is integer.
• And we cleaned up the demonstration code while we were in there.

GEMD v0.11.0 is released!

Improvements

• This release include a number of improvements to one of our pieces of demonstration code (demo/cake). Many more annotations and better coding and naming practice are now available throughout the example.
• We've also made it possible to change the scope of the demo, which in turn makes it possible for multiple versions of the data structures it generates to coexist without colliding keys.

GEMD v0.10.0 is released!

What's New

• We've updated the guidance for contributing to reflect better practice. This includes adding type hints and not allowing positional arguments for methods that have multiple arguments.

Improvements

• The string representation of LinkByUID objects has been changed to match their field names.

Fixes

• If the flatten method is invoked on a BaseEntity, it now includes that object in the returned list.

GEMD v0.9.0 is released!

Improvements

• Some ambiguous units strings (e.g. t) were removed to prevent assignment of the wrong units.
• Bounds are now optional on object templates and no longer copied from the corresponding attribute template.

GEMD v0.8.0 is released!

What’s New

You can now choose your preferred default scope. We've added an argument to our GEMDJson constructor so that the default scope when auto-generating ids in serialization (formerly auto) can suit your need.

Fixes

Following the removal of support for Python < 3.5, we still were importing enum34, which was causing some problems with the most current version of the core packages. This has been corrected.