Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: comicrelief/lambda-wrapper
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.0.0-beta.13
Choose a base ref
...
head repository: comicrelief/lambda-wrapper
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.0.0-beta.14
Choose a head ref
  • 3 commits
  • 4 files changed
  • 1 contributor

Commits on Dec 15, 2023

  1. refactor: Rename SQS message model class (#1191)

    Change the name of the class to match the name exported from the package
    index.
    
    This should not be a breaking change because the class is the default
    export of its module. Just in case there is some contrived case that
    depends on the class's `name` attribute, we'll include this in the
    v2.0.0 major release.
    
    Jira: [ENG-2733]
    seb-cr authored Dec 15, 2023
    Configuration menu
    Copy the full SHA
    4581d61 View commit details
    Browse the repository at this point in the history

Commits on Dec 18, 2023

  1. docs: Add instructions to SQSMessageModel (#1190)

    The main point I wanted to add here is that this model is for _received_
    messages. I've also added a bit of explanation about its intended use
    with `SQSService`.
    
    Jira: [ENG-2733]
    seb-cr authored Dec 18, 2023
    Configuration menu
    Copy the full SHA
    7bac68d View commit details
    Browse the repository at this point in the history

Commits on Jan 19, 2024

  1. feat: Throw by default from failed SQS publish (#1194)

    Currently, sending an SQS message using `SQSService` does not throw an
    error by default. This has caught us out a couple of times where we were
    expecting a failure. The `failureMode` parameter was added to opt in to
    throwing errors, to avoid introducing a breaking change in v1.
    
    In v2 we'll throw errors by default, and you'll have to opt _out_ of
    this behaviour.
    
    BREAKING CHANGE: `SQSService#publish` throws by default instead of
    handling errors. To maintain old behaviour, you can pass `"catch"` in
    the `failureMode` parameter.
    seb-cr authored Jan 19, 2024
    Configuration menu
    Copy the full SHA
    dca7620 View commit details
    Browse the repository at this point in the history
Loading