<itemvalue="feat: add startup bulletin; switch to edit mode when click text on md preview."/>
<itemvalue="on Tap"/>
<itemvalue="on Tap"/>
<itemvalue="Handles errors emitted by this [Future]. This is the asynchronous equivalent of a "catch" block. Returns a new [Future] that will be completed with either the result of this future or the result of calling the `onError` callback. If this future completes with a value, the returned future completes with the same value. If this future completes with an error, then [test] is first called with the error value. If `test` returns false, the exception is not handled by this `catchError`, and the returned future completes with the same error and stack trace as this future. If `test` returns `true`, [onError] is called with the error and possibly stack trace, and the returned future is completed with the result of this call in exactly the same way as for [then]'s `onError`. If `test` is omitted, it defaults to a function that always returns true. The `test` function should not throw, but if it does, it is handled as if the `onError` function had thrown. Note that futures don't delay reporting of errors until listeners are added. If the first `catchError` (or `then`) call happens after this future has completed with an error then the error is reported as unhandled error. See the description on [Future]. The `Function` below stands for one of two types: - (dynamic) -> FutureOr<T> - (dynamic, StackTrace) -> FutureOr<T> Given that there is a `test` function that is usually used to do an `isCheck` we should also expect functions that take a specific argument."/>
<itemvalue="Handles errors emitted by this [Future]. This is the asynchronous equivalent of a "catch" block. Returns a new [Future] that will be completed with either the result of this future or the result of calling the `onError` callback. If this future completes with a value, the returned future completes with the same value. If this future completes with an error, then [test] is first called with the error value. If `test` returns false, the exception is not handled by this `catchError`, and the returned future completes with the same error and stack trace as this future. If `test` returns `true`, [onError] is called with the error and possibly stack trace, and the returned future is completed with the result of this call in exactly the same way as for [then]'s `onError`. If `test` is omitted, it defaults to a function that always returns true. The `test` function should not throw, but if it does, it is handled as if the `onError` function had thrown. Note that futures don't delay reporting of errors until listeners are added. If the first `catchError` (or `then`) call happens after this future has completed with an error then the error is reported as unhandled error. See the description on [Future]. The `Function` below stands for one of two types: - (dynamic) -> FutureOr<T> - (dynamic, StackTrace) -> FutureOr<T> Given that there is a `test` function that is usually used to do an `isCheck` we should also expect functions that take a specific argument."/>
