Skip to content

v1.0.2

Compare
Choose a tag to compare
@camargo camargo released this 25 Jan 23:35
· 450 commits to develop since this release
7df7089

Summary of New Features

  • Major update to timeline layer editing. The timeline editor now has the ability to add, update, delete, and customize layers.
  • The delete key now works for deleting activities when focused on the timeline.
  • A clear error console button has been added for errors that are dismissible.
  • Tables now have resize options in their context menu.
  • Scheduling goals and conditions now clearly show their associated plan.
  • The create plan date picker now pre-populates the end time with the start time if a start time is selected.
  • The UI Docker image now is auto-built for multiple machine architectures.
  • Ellipsis have been added to the activity types list to account for overflow of long activity names.
  • Migrated to a new documentation site: https://nasa-ammos.github.io/aerie-docs

Breaking Changes

Please see our latest upgrade guide for complete instructions for upgrading from 1.0.1 to 1.0.2.

  • The UI view /view/validate endpoint was moved from the gateway to the UI server. Any downstream code must now POST to /view/validate on the UI server. The UI server has the same API so no other changes are needed other than changing the target server. So if you are running Aerie locally with the default ports and configuration you would change http://localhost:9000/view/validate to http://localhost/view/validate.

  • The UI view schema has replaced Regex filters with lists specifying the given type. To show activities in a timeline layer you now need to specify the list of activity types you want to show. For example to show activities with type BakeBananaBread, BananaNap, and BiteBanana you can do:

    {
      "filter": {
        "activity": {
          "types": ["BakeBananaBread", "BananaNap", "BiteBanana"]
        }
      }
    }

    Similarly for resources you now need to specify a resource name you want to show. For example to show the /peel resource you can do:

    {
      "filter": {
        "resource": {
          "names": ["/peel"]
        }
      }
    }

    These replace the type and name field from the activity and resource filters respectively. Any downstream code needs to be updated to account for this.

What's Changed

New Features

Bug Fixes

  • Forward events to recursive calls of the SplitGrid component by @AaronPlave in #312
  • Do not clear last toast when same message is spammed quickly by @duranb in #329
  • Update showOnInit to showOnCreate by @duranb in #336
  • Add ellipsis to list item by @camargo in #348
  • Replace simulation subscriptions with queries by @camargo in #351

Refactoring

Testing

  • Output JUnit XML for unit tests by @camargo in #316
  • Update expansion rule to latest format in e2e test by @camargo in #355

Continuous Integration

  • Add multi-arch image build, update action versions by @skovati in #322

Build System and Dependencies

Full Changelog: v1.0.1...v1.0.2