functional_status_codes 1.1.0

This package offers a functional approach to handling HTTP status codes.

1.1.0

Contains breaking changes in maybeMapStatusCode method on num. Please follow migration guide below.

• refactor!: orElse parameter in maybeMapStatusCode now returns input value in order to handle this unregistered status code.

• docs: updated documentation of breaking update.

• docs: added topics to pubspec.yaml.

• chore: updated SDK upper-bound to 4.0.0.

• refactor: replaced deprecated fields in analysis_options.yaml with new ones.

Since maybeMapStatusCode now returns input value, you will have to adjust your existing code, for example:

Replace from:

...
final statusCode = response.statusCode;
...
statusCode.maybeMapStatusCode(
    orElse: () => handleUnregisteredStatusCode(statusCode),
    isSuccess: handleSuccessStatusCode,
    ...
);
...

Use this instead:

...
final statusCode = response.statusCode;
...
statusCode.maybeMapStatusCode(
    orElse: handleUnregisteredStatusCode,
    isSuccess: handleSuccessStatusCode,
    ...
);
...

Or if you are using tear-off syntax, replace:

...
final statusCode = response.statusCode;
...
statusCode.maybeMapStatusCode(
    orElse: handleUnregisteredStatusCode,
    isSuccess: handleSuccessStatusCode,
    ...
);
...

With this instead:

...
final statusCode = response.statusCode;
...
statusCode.maybeMapStatusCode(
    orElse: (_) => handleUnregisteredStatusCode(),
    isSuccess: handleSuccessStatusCode,
    ...
);
...

1.0.6

• docs: fixed contribution guidelines reference link.

1.0.5

• docs: changed screenshot to webp format.
• ci(github): added automatic pub.dev publishing workflow.

1.0.4

• docs: added screenshot to pub.dev, no code changes.

1.0.3

• refactor: small refactoring in generated functional enums extensions and dependencies update.

1.0.2

• docs: removing unnecessary information from the documentation.

1.0.1

• docs: update README documentation.

1.0.0

• initial version.