Of note, because there is only one HTTP client involved in sending both single messages and batch messages, the WithEndpoint() override will apply to both endpoints, even though the paths of the original endpoints differ. There's no easy way around this without refactoring of the code to use two different HTTP clients and in practice, somebody wanting to override this endpoint can likely cope with this limitation by dealing with the different requests based on the incoming content.
This pull request addresses #385.
Of note, because there is only one HTTP client involved in sending both single messages and batch messages, the
WithEndpoint()override will apply to both endpoints, even though the paths of the original endpoints differ. There's no easy way around this without refactoring of the code to use two different HTTP clients and in practice, somebody wanting to override this endpoint can likely cope with this limitation by dealing with the different requests based on the incoming content.