Skip to content

v1.9.1

Compare
Choose a tag to compare
@jberends jberends released this 27 Jun 12:34

1.9.1 (27JUN17)

  • Improved testing. Notably on the new inspector objects. No functional change only that we want to reach our goal of 95% test coverage! Thanks to @raduiordache (#137)

1.9.0 (23JUN17)

  • Added a major new feature to create Customizations of activities in KE-chain 2 all programmatically and pythonic. We provide building block classes such as SuperGrid, PaginatedGrids and PropertyGrids to make your own task customization. All is documented with examples. A validation() method is available. (#110)
    >>> my_task = project.activity('my task')
    >>> bike = project.part(name='Bike')
    >>> customization = Customization()  # init customization object for the task
    >>> my_prop_grid = PropertyGrid(part=bike, title=bike.name)  # create a PropertyGrid
    >>> customization.add_component(my_prop_grid)  # add PropertyGrid to the Customization component list
    >>> customization.validate()  # you can validate the customization
    >>> my_task.customize(customization)  # upload/set the Customization. Ensure you have data access set correctly.
  • Updated the way the Activity.customize() method works. This method now accepts a Customization object or a josn (as a python dict). It uses the Customization.validate() method to validate if it conforms to the required json structure before uploading it to KE-chain.
  • Improved test coverage and refactored the HTTP codes to human readable form. (#128)
  • Added the ability to edit the description of property models. This was included in Part.create_property(... description=...) (#135)
  • Add Part.as_dict() method to retrieve the properties of a part in pykechain as a python dictionary as {<property_name> : <property_value>} (#131)
  • Added the ability to optionally update the name of a part together with the value of its properties. See the Part.update() method. (#126)
  • Deprecated the Activity.create_activity() method in favor of Activity.create(). Use the latter. Will warn with a DeprecationWarning until removed.