Skip to content

v0.3.0
Compare
Choose a tag to compare
@cmgrote cmgrote released this 03 Feb 14:56
v0.3.0
83a6b48

🎉 New features

  • Adds simplified set of helpers to construct searches through the QueryFactory
  • Adds validation of connection admins during both creation and update of a connection
  • Adds validation of users and groups specified in purpose policies

⛑️ Breaking changes

  • QueryFactory methods have changed to match the naming convention used for the simplification and the fact that searchable fields are now enumerated rather than simple strings:
    • active() -> beActive()
    • archived() -> beArchived()
    • withLineage() -> haveLineage()
    • withType() -> beOfType()
    • withSuperType() -> haveSuperType()
    • withCertificate() has been removed. Instead use have(KeywordFields.CERTIFICATE_STATUS).eq()
    • withExactName() has been removed. Instead use have(KeywordFields.NAME).eq()
    • whereQualifiedNameStartsWith() has been removed. Instead use have(KeywordFields.QUALIFIED_NAME).startingWith()
    • withAnyValueFor() has been removed. Instead use have(<field>).present()
    • withAtLeastOneClassification() -> beClassifiedByAtLeastOneOf(), which now takes a collection of human-readable classification names rather than internal hashed-string classification IDs
    • withAtLeastOneTerm() -> beDefinedByAtLeastOneOf()

(Note: we're reserving the right to make breaking changes to the SDK prior to a 1.0.0 release, without incrementing the major version. Once we hit 1.0.0, we'll adhere to https://semver.org)

🐞 Bug fixes

  • Fixed an issue where all attributes of type PopularityInsights were incorrectly (de)serialized
  • Fixed an issue where a typedef with certain characters in its name (like spaces) could not be deleted

🥗 QOL improvements

  • Enumerates all searchable fields to avoid typos or choosing the wrong indexed field for a particular type of search
  • Simplified helpers in QueryFactory for building complex queries, aggregations, and sorting
  • Simplified helpers in QueryFactory for retrieving results of metrics-based aggregations
  • It should no longer be possible to create a connection that you are locked out of due to making a typo in the details of any roles, groups or users you set as connection admins
  • It should no longer be possible to create a policy on a purpose that applies to non-existent users or groups
Assets 2
Loading