Bump http, fpdart, mocktail, rxdart and fhir_yaml

Open dependabot[bot] opened this issue 2 years ago • 0 comments

Bumps http, fpdart, mocktail, rxdart and fhir_yaml. These dependencies needed to be updated together. Updates http from 0.13.2 to 0.13.5

Commits

See full diff in compare view

Updates fpdart from 0.2.0 to 0.4.0

Release notes

Sourced from fpdart's releases.

v0.4.0

Added extension methods to work with nullable types (T?)

From T? to fpdart's types

toOption

toEither

toTaskOption

toIOEither

toTaskEither

toTaskEitherAsync

fromNullable (Either, IOEither, TaskOption TaskEither)

fromNullableAsync (TaskEither)

From fpdart's types to T?

toNullable (Either)
/// [Option] <-> `int?`
int? value1 = 10.toOption().map((t) => t + 10).toNullable();
bool? value2 = value1?.isEven;
/// bool? -> [Either] -> int?
int? value3 = value2
.toEither(() => "Error")
.flatMap((a) => a ? right<String, int>(10) : left<String, int>("None"))
.toNullable();
/// int? -> [Option]
Option<int> value4 = (value3?.abs().round()).toOption().flatMap(Option.of);
Added toIOEither to Either

Removed parameter from Either fromNullable [⚠️ BREAKING CHANGE]
final either = Either<String, int>.fromNullable(value, (r) => 'none');
/// 👆 Removed the value (r) (it was always null anyway 💁🏼‍♂️) 👇
final either = Either<String, int>.fromNullable(value, () => 'none');
Added chainEither to TaskEither

Added safeCast (Either and Option)

Added safeCastStrict (Either and Option)
int intValue = 10;
/// Unhandled exception: type 'int' is not a subtype of type 'List<int>' in type cast
final waitWhat = intValue as List<int>;
final first = waitWhat.first;
/// Safe 🎯
final wellYeah = Either<String, List<int>>.safeCast(
intValue,
</tr></table>

... (truncated)

Changelog

Sourced from fpdart's changelog.

v0.4.0 - 16 December 2022

Added extension methods to work with nullable types (T?)

From T? to fpdart's types

toOption

toEither

toTaskOption

toIOEither

toTaskEither

toTaskEitherAsync

fromNullable (Either, IOEither, TaskOption TaskEither)

fromNullableAsync (TaskEither)

From fpdart's types to T?

toNullable (Either)
/// [Option] <-> `int?`
int? value1 = 10.toOption().map((t) => t + 10).toNullable();
bool? value2 = value1?.isEven;
/// bool? -> [Either] -> int?
int? value3 = value2
.toEither(() => "Error")
.flatMap((a) => a ? right<String, int>(10) : left<String, int>("None"))
.toNullable();
/// int? -> [Option]
Option<int> value4 = (value3?.abs().round()).toOption().flatMap(Option.of);
Added toIOEither to Either

Removed parameter from Either fromNullable [⚠️ BREAKING CHANGE]
final either = Either<String, int>.fromNullable(value, (r) => 'none');
/// 👆 Removed the value (r) (it was always null anyway 💁🏼‍♂️) 👇
final either = Either<String, int>.fromNullable(value, () => 'none');
Added chainEither to TaskEither

Added safeCast (Either and Option)

Added safeCastStrict (Either and Option)
int intValue = 10;
/// Unhandled exception: type 'int' is not a subtype of type 'List<int>' in type cast
final waitWhat = intValue as List<int>;
final first = waitWhat.first;
/// Safe 🎯
final wellYeah = Either<String, List<int>>.safeCast(
intValue,
</tr></table>

... (truncated)

Commits

201b3d0 Open meteo example (#63)
44884d7 release v0.4.0
2bcda29 examples of tasks and futures
ebe22ad added examples to README
458f673 updated CHANGELOG
beec642 README for open meteo api example
17dd4ba refactoring and removed unneeded code
7a83ab6 completed tests for meteo location
7d69212 valid tests for fpdart open meteo api
553c2af tests for open meteo api
Additional commits viewable in compare view

Updates mocktail from 0.1.4 to 0.3.0

Release notes

Sourced from mocktail's releases.

mocktail-image-network-v0.3.0

feat: upgrade to mocktail ^0.3.0

mocktail-v0.3.0

BREAKING feat: add support for type argument matching (#66) (@renancaraujo)

feat: improve verifyNoMoreInteractions failure message (#118)

docs: improve argument matcher documentation in README (#102)

docs: fix typo in _registerMatcher inline docs (#101)

docs: minor snippet fixes in README (#94)

docs: enhance example to illustrate more use cases

mocktail-image-network-v0.3.0-dev.1

feat: upgrade to mocktail ^0.3.0-dev.1

mocktail-v0.3.0-dev.1

BREAKING feat: add support for type argument matching (#66)

docs: minor snippet fixes in README (#94)

docs: enhance example to illustrate more use cases

mocktail-image-network-v0.2.0

feat: upgrade to mocktail ^0.2.0

mocktail-v0.2.0

BREAKING refactor: remove generic from registerFallbackValue

docs: add FAQs to README

Commits

c4ca18f chore(mocktail): v0.3.0 (#117)
447575a feat(mocktail): improve verifyNoMoreInteractions failure message (#118)
70e915f docs(mocktail): improve argument matcher documentation in README (#102)
c9471cb docs: fix typo in _registerMatcher inline docs (#101)
6dcdef0 chore(mocktail_image_network): v0.3.0-dev.1 (#99)
ed5aa6a chore(mocktail): v0.3.0-dev.1 (#98)
6db5916 refactor(mocktail): type arg support improvements (#97)
eee9d4b refactor(mocktail): resolve analysis warnings (#96)
461be1f feat!: support type arguments (#67)
4614a29 docs: fix expected value in README (#94)
Additional commits viewable in compare view

Updates rxdart from 0.26.0 to 0.27.7

Release notes

Sourced from rxdart's releases.

0.27.7

https://pub.dev/packages/rxdart/versions/0.27.7

Fixed

Subject

Only call onAdd and onError if the subject is not closed. This ensures BehaviorSubject and ReplaySubject do not update their values after they have been closed.

Subject.stream now returns a read-only Stream. Previously, Subject.stream was identical to the Subject, so we could add events to it, for example: (subject.stream as Sink<T>).add(event). This behavior is now disallowed, and will throw a TypeError if attempted. Use Subject.sink/Subject itself for adding events.

Change return type of ReplaySubject<T>.stream to ReplayStream<T>.

Internal refactoring of Subject.addStream.

What's Changed

fix(subject): only call onAdd and onError if the subject is not closed by @hoc081098 in ReactiveX/rxdart#698

refactor(subject): Subject.stream now returns a read-only Stream by @hoc081098 in ReactiveX/rxdart#699

refactor(subject): addStream by @hoc081098 in ReactiveX/rxdart#700

chore(publish): prepare for v0.27.7 by @hoc081098 in ReactiveX/rxdart#701

Full Changelog: https://github.com/ReactiveX/rxdart/compare/0.27.6...0.27.7

0.27.6

https://pub.dev/packages/rxdart/versions/0.27.6

Rx.using/UsingStream: resourceFactory can now return a Future. This allows for asynchronous resource creation.

Rx.range/RangeStream: ensure RangeStream is only listened to once.

What's Changed

fix(range): make sure RangeStream can only be listened to once by @hoc081098 in ReactiveX/rxdart#690

fix(range): ensure RangeStream is only listened to once by @hoc081098 in ReactiveX/rxdart#694

refactor(Rx.using): resourceFactory can return a Future by @hoc081098 in ReactiveX/rxdart#696

chore(publish): prepare for v0.27.6 by @hoc081098 in ReactiveX/rxdart#697

Full Changelog: https://github.com/ReactiveX/rxdart/compare/0.27.5...0.27.6

0.27.5

https://pub.dev/packages/rxdart/versions/0.27.5

Bug fixes

... (truncated)

Changelog

Sourced from rxdart's changelog.

0.27.7 (2022-11-16)

Fixed

Subject

Only call onAdd and onError if the subject is not closed. This ensures BehaviorSubject and ReplaySubject do not update their values after they have been closed.

Subject.stream now returns a read-only Stream. Previously, Subject.stream was identical to the Subject, so we could add events to it, for example: (subject.stream as Sink<T>).add(event). This behavior is now disallowed, and will throw a TypeError if attempted. Use Subject.sink/Subject itself for adding events.

Change return type of ReplaySubject<T>.stream to ReplayStream<T>.

Internal refactoring of Subject.addStream.

0.27.6 (2022-11-11)

Rx.using/UsingStream: resourceFactory can now return a Future. This allows for asynchronous resource creation.

Rx.range/RangeStream: ensure RangeStream is only listened to once.

0.27.5 (2022-07-16)

Bug fixes
Fix issue #683: Throws runtime type error when using extension methods on a Stream<R> but its type annotation is Stream<T>, R is a subtype of T (covariance issue with StreamTransformer).
Stream<num> s1 = Stream<int>.fromIterable([1, 2, 3]);
// throws "type 'SwitchMapStreamTransformer<num, num>' is not a subtype of type 'StreamTransformer<int, num>' of 'streamTransformer'"
s1.switchMap((v) => Stream.value(v));
Stream<int?> s2 = Stream<int>.fromIterable([1, 2, 3]);
// throws "type 'SwitchMapStreamTransformer<int?, int?>' is not a subtype of type 'StreamTransformer<int, int?>' of 'streamTransformer'"
s2.switchMap((v) => Stream.value(v));
Extension methods were previously implemented via stream.transform(streamTransformer), now via streamTransformer.bind(stream) to avoid this issue.
Fix concatEager: activeSubscription should be changed to next subscription.
Code refactoring

Change return type of pairwise to Stream<List<T>>.

0.27.4 (2022-05-29)

Bug fixes

... (truncated)

Commits

3d1b6c0 chore(publish): prepare for v0.27.7 (#701)
b0d6ad1 refactor(subject): addStream (#700)
e1f6cd9 refactor(subject): Subject.stream now returns a read-only Stream (#699)
1a8fcef ci: add dart 2.17.0
45f8c5e fix(subject): only call onAdd and onError if the subject is not closed (#...
8916c7c chore(publish): prepare for v0.27.6 (#697)
9464cdd refactor(Rx.using): resourceFactory can return a Future (#696)
c0566b4 fix(range): ensure RangeStream is only listened to once (#694)
58c82c0 fix(range): make sure RangeStream can only be listened to once (#690)
e13dad0 prepare for v0.27.5 (#688)
Additional commits viewable in compare view

Updates fhir_yaml from 0.4.0 to 0.9.0

Commits

See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
@dependabot use these labels will set the current labels as the default for future PRs for this repo and language
@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Feb 13 '23 13:02 dependabot[bot]