Skip to content
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.

feat: Add ResourceConflictError #74

Merged
merged 2 commits into from
Aug 5, 2021
Merged

Conversation

ssvegaraju
Copy link
Contributor

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@ssvegaraju ssvegaraju marked this pull request as ready for review August 5, 2021 07:52
@github-actions github-actions bot added the size/s label Aug 5, 2021
@ssvegaraju ssvegaraju requested a review from carvantes August 5, 2021 07:53
Copy link
Contributor

@carvantes carvantes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

Just make sure to update the PR name(and the resulting merge commit msg) before merging.

Commit message should be about the changes in this package, not about the overall feature that we are working on. Also, be careful about the distinction between fix: and feat: as they end up bumping the version in different ways. https://www.conventionalcommits.org/en/v1.0.0/

A better commit msg would be:

feat: Add ResourceConflictError

@carvantes
Copy link
Contributor

Also, you need to merge and release this PR and then update the interface version on awslabs/fhir-works-on-aws-routing#109 to have unit tests pass there. This is not a feature branch, so we need to release things in order

@ssvegaraju ssvegaraju changed the title fix: TransactionConflict Errors Should be User Errors feat: Add ResourceConflictError Aug 5, 2021
@ssvegaraju ssvegaraju merged commit fa3facc into mainline Aug 5, 2021
@ssvegaraju ssvegaraju deleted the feat-ResourceConflictError branch August 5, 2021 19:45
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants