Skip to content

fix: Delete confusing assertion in test - #307

Draft
supersven wants to merge 1 commit into
bitemyapp:masterfrom
supersven:improve-version-conflict-test
Draft

fix: Delete confusing assertion in test#307
supersven wants to merge 1 commit into
bitemyapp:masterfrom
supersven:improve-version-conflict-test

Conversation

@supersven

Copy link
Copy Markdown
Contributor

The assertion implied that a version conflict can lead to a Right value (maybe for either ElasticSearch or OpenSearch.) However, the parsing logic would force this to be a Left value.

insertedConflict <- tryEsError $ insertData' cfg
case insertedConflict of
Right (res', _) -> liftIO $ isVersionConflict res' `shouldBe` True
Right _ -> liftIO $ expectationFailure "This should never not happen."

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Isn't it redundant?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

That's a too much Git magic to create small PRs-mistake. Sorry for the noise - I'm fixing it.

The assertion implied that a version conflict can lead to a Right
value (maybe for either ElasticSearch or OpenSearch.) However, the
parsing logic would force this to be a Left value.
@supersven
supersven force-pushed the improve-version-conflict-test branch from 05ba926 to 72b2168 Compare November 6, 2024 08:06
@blackheaven
blackheaven force-pushed the master branch 4 times, most recently from 19e7d73 to 3789abe Compare October 6, 2025 23:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants