- Add support for Dart null safety (#155)
- SDK / Dependency Versioning:
- Increase minimum Dart SDK version from
2.11.0
to2.13.0
. - Increase minimum
react
version from6.0.1
to7.0.0
.
- Increase minimum Dart SDK version from
- SDK / Dependency Versioning:
- Raise max allowed versions of
react
andflux
dependencies (#152)
- Remove usages of deprecated APIs that will be removed in react-dart 7.0.0
- Bump dependencies:
meta: ^1.8.0
,test: ^1.21.1
- Unpin meta dependency
- Internal updates (dev_dependencies, CI)
- Internal updates (dev_dependencies, cleanup)
- Set minimum Dart SDK to 2.11.0
- Remove deprecated authors field from pubspec.yaml
- Widen Dependency Ranges Blocking Dart 2.13
- Switch to Github CI
- Added support for searching within ShadowDOM roots to
queryByTestId
andqueryAllByTestId
.
- Widen over_react and react version constraints in preparation for v4.0.0 and v6.0.0, respectively.
Re-tag of 2.10.0 release which was not released correctly
- Only expect
propTypes
errors in DDC runtime.
-
Fix prop forwarding tests false positives
Tests that had
commonComponentTests.getUnconsumedPropKeys()
returning a list of keys that included keys within mixins that were actually being consumed by the component were not failing as expected.e.g. this situation should have resulted in test failures, but it did not:
Component's consumedProps:
@override get consumedProps => propsMeta.forMixins({ SomePropsMixin, });
Component's commonComponentTests:
group('common component tests', () { commonComponentTests(ComponentFactory, getUnconsumedProps: (propsMeta) => [ ...propsMeta.forMixin(SomePropsMixin).keys, ]); });
- Add
Object.values
shim for MSIE 11.
- Normalize the behavior of the
render()
utility function betweenUiComponent
andUiComponent2
components. - Un-deprecate the
throwsPropError*
matchers.
- Fix typo in
logsPropError
matcher to ensure consumers can easily migrate fromthrowsPropError
when appropriate.
- Move
isComponent2
call inside atest
block to address consumer issues when the provided factory accesses values that are initialized withinsetUp
.
- Move
getPropsMeta
call inside atest
block to address consumer issues when the provided factory has required props that come fromsetUp
-initialized variables.
- Add Component Version Auto Detection
- Re-instate prop forwarding tests for new over_react component boilerplate
- Update mount, render, and renderAttachedToDocument to automatically run component lifecycle in the same zone as the test.
- This fixes some
print
statements from being swallowed and some failingexpect
s from not failing tests properly
- This fixes some
- Add propTypes testing utilities
- Drop support for React 15
- Support Component2 in commonComponentTests
- Add support for React 16 (raise upper bound of
react
to allow 5.x,over_react
to allow 3.x) - Fix documentation link
- Accommodate findAllInRenderedTree being passed text nodes in React 16
- Update references to old JS interop helpers
- Update contributing docs
- Work around a bug in DDC where SvgElement className isn't String
- Widen over_react range to allow 2.0.0
- Update component boilerplate in preparation for over_react 2.0.0
- Update component boilerplate in preparation for over_react 2.0.0
New Features
- Dart 2 compatible!
Breaking Changes
-
The
getComponentPropKeys()
andtestPropForwarding()
functions have been removed, as they depended ondart:mirrors
. Once there is a Dart-2-only release ofover_react
, this function will be re-added and will rely on information generated by the builder rather than using mirrors. -
The
commonComponentTests()
function no longer callstestPropForwarding()
since it has been removed. In other words, theshouldTestPropForwarding
parameter is effectively a no-op untiltestPropForwarding()
can be re-added.
Bugs Fixed
- Sync common component test src with the lib it originated from.
New Features
- #11: Add some test utilities that were left in
over_react
when the library was first created.
Misc
- #8: Update prop error message to make it more DDC friendly
Initial public release of library.