1.2.0

What's Changed

• Guard against reusing EmpireViewModels instances across multiple EmpireWidgets by @jshep23 in #96

New Contributors

• @j21-dev made their first contribution in #97

Full Changelog: 1.1.0...1.2.0

1.1.0

What's Changed

• EmpireListProperty New Features (Insert, Sublist, toString) by @jshep23 in #93
• Version 1.1.0 by @mdryden in #94

Full Changelog: 1.0.0...1.1.0

1.0.0

What's Changed

• Release 1.0.0 🎉 by @mdryden in #90

Full Changelog: 0.12.0...1.0.0

0.12.0

What's Changed

• Added new optional argument on EmpireProperty called setAsOriginal. Setting this to true will update the original value on change.
• Updated some stale documentation

Pull Requests

• Add setAsOriginal argument on EmpireProperties by @jshep23 in #87
• Empire Int and Double Property Documentation Updates by @jshep23 in #88
• 0.12.0 by @jshep23 in #89

Full Changelog: 0.11.0...0.12.0

0.11.0

What's Changed

• Fixed the a bug where the busy property on an EmpireViewModel returned an incorrect value if there are multiple different busyTaskKeys assigned.
• Added additional functionality to EmpireListProperty to bring them closer in line with a plain Dart List object. The following has been added:
  • first (read-only property)
  • last (read-only property)
  • reversed (read-only property)
  • single (read-only property)
  • where (function)
  • firstWhere (function)
  • firstWhereOrNull (function)

BREAKING CHANGES

We found some issues with the arithmetic operator overrides in the EmpireIntProperty and EmpireDoubleProperty classes. For details on the issue, please see GitHub Issue #83. Ultimately, we had to scrap the operator overrides and implement the arithmetic operations as functions.

• Implemented arithmetic functions for EmpireIntProperty and EmprieDoubleProperty, and their nullable variants
• Removed the operator overrides

We have also made changes to the constructor signature for EmpireNullableDateTimeProperty and EmpireNullableIntProperty. This was to bring them in line with the other Empire Nullable properties.

• Updated EmpireNullableDateTimeProperty and EmpireNullableIntProperty constructors so the value argument is optional instead of a required positional argument.

Pull Requests

• List property improvements by @jshep23 in #82
• Optional Value Constructor Argument on Nullable Properties by @jshep23 in #80
• EmpireIntProperty and EmpireDoubleProperty Arithmetic Fixes by @jshep23 in #84
• Fix setBusyStatus on EmpireViewModel by @jshep23 in #85
• 0.11.0 Release by @jshep23 in #86

Full Changelog: 0.10.0...0.11.0

0.10.0

What's Changed

• #32 VScode extension by @mdryden in #73
• VS Code Extension Publishing Tweaks by @mdryden in #74
• Extension icon fix by @mdryden in #75
• Reset All Empire Properties by @jshep23 in #76
• 0.10.0 Release by @jshep23 in #77

Full Changelog: 0.9.1...0.10.0

0.9.1

What's Changed

• Updated README to reflect the new empireProps change in the 0.9.0 release.

Pull Requests

• Release 0.9.1 - README Update by @jshep23 in #71

Full Changelog: 0.9.0...0.9.1

0.9.0

What's Changed

• Added increment and decrement functions to the EmpireIntProperty
• Updated the example project
• Updated README to reflect the property initialization refactor changes
• Added many factory constructors to various Empire Properties. (eg) EmpireDateTimeProperty.now() to create a DateTime property defaulted to the current Date/Time

BREAKING CHANGES

• We've redesigned and refactored how you go about initializing an EmpireProperty, and made it more dart-ly (it's a word now).
• Empire Properties in an EmpireViewModel are no longer initialized via a initProperties function that previously needed to be overridden, and was called by the ViewModel constructor behind the scenes. You can now instantiate a property as you would any other Dart object; via it's own constructor.
• There is a new getter List property called empireProps that must be overridden in a ViewModel. This should return the Empire Properties that you want to be reactive. (eg) Update the UI on change.
• This change also allowed us to remove the requirement that all Empire Properties be defined with the late keyword.
• This change also allows consumers to inject Empire Properties into the ViewModel.
• Reorganized the library exports

In general, we will avoid major breaking changes if at all possible. In this case, as we approach a stable 1.0.0 release, we felt it was an overall improvement to the library based on valuable user feedback.

Pull Requests

• Add Increment and Decrement to EmpireIntProperty by @jshep23 in #67
• Publish to pub when release is published by @mdryden in #69
• Empire Property Initialization Refactor by @jshep23 in #68
• 0.9.0 Release by @jshep23 in #70

Full Changelog: 0.8.3...0.9.0

0.9.0-dev.1

What's Changed

• Add Increment and Decrement to EmpireIntProperty by @jshep23 in #67
• Publish to pub when release is published by @mdryden in #69

• Added increment and decrement functions to the EmpireIntProperty

BREAKING CHANGES

• We've redesigned and refactored how you go about initializing an EmpireProperty, and made it more dart-ly(it's a word now).

• Empire Properties in an EmpireViewModel are no longer initialized via a initProperties function that previously needed to be overridden, and was called by the ViewModel constructor behind the scenes. You can now instantiate a property as you would any other Dart object; via it's own constructor.

• This change also allowed us to remove the requirement that all Empire Properties be defined with the late keyword.

• This change also allows consumers to inject Empire Properties into the ViewModel.

• There is a new getter List property called props that must be overridden in a ViewModel. This should return the Empire Properties that you want to be reactive. (eg) Update the UI on change.

• We've also added many factory constructors to various Empire Properties. (eg) EmpireDateTimeProperty.now() to create a DateTime property defaulted to the current Date/Time

• Reorganized the library exports

• Updated the example project

Full Changelog: 0.8.3...0.9.0-dev.1

0.8.3

What's Changed

• Update library description by @jshep23 in #65

Full Changelog: 0.8.2...0.8.3