Developers :: 3.0 Wishlist

What should we include in the 3.0 release of signal-analog?

• Charts should enforce that published Data statements in a Program are assigned to an upper case variable

  • i.e. Data('foo').publish(label='c') or Data('foo').publish() should no longer be allowed
    • Instead it might look like Assign('A', Data('foo').publish(label='A'))
    • Could also be implemented as a Program validation method
  • Why? this will automatically promoted v2 charts to the "lego-brick" builder ui and makes it easy for new users to understand how their SignalFlow programs are translated to the UI

• Remove py2 support

  • Why? Py2 is almost EOL, and we'd like to use newer features of Python reliably (e.g. async)

• Refactor update logic to: remove it from resource objects themselves in a SignalFx client, and implement async functionality for resources with many child resources that require updates (e.g. dashboards with many charts)

  • Why? After recent API changes signal_analog is pretty dog slow. Refactoring/cleaning up logic will allow us to cater to newer API features while speeding up existing resource updates by making use of native async features in Py3