search

pact-foundation / roadmap

Developer Relations @ Pact - Your map to the Pact landscape for all-comers (maintainers, contributors, users, newbies)
https://pact.io/
MIT License
41 stars 7 forks source link

Should pacticipant names be case insensitve? #66

Open canny[bot] opened 5 months ago

canny[bot] commented 5 months ago

It would be awesome if either: 1) Pacticipant names were case insensitve or 2) The broker warned when publishing or retrieving a pact if the pacticipant name differs only in case from another This was indirectly suggested by Subrahmanyam Rentala on slack: At the consumer side I provided the provider name as : ABc and at the provider side it was ABC, and again error was not user friendly to investigate

https://pact.canny.io/admin/board/feature-requests/p/should-pacticipant-names-be-case-insensitve

canny[bot] commented 5 months ago

This issue has been linked to a Canny post: Should pacticipant names be case insensitve? :tada:

YOU54F commented 5 months ago

Dmitry Munda - September 8, 2021

same goes maybe with tags

YOU54F commented 5 months ago

Subrahmanyam Rentala - September 8, 2021

Its a simple mistake we do, but would be nice to have an appropriate error handling, or else it would be difficult to troubleshoot the issue.

YOU54F commented 5 months ago

Beth - September 25, 2021

There is support for case insensitive resource name matching in the broker, but it's not supported everywhere, and I wouldn't recommend using it. I've been meaning to deprecate support for that actually, as I think it could easily lead to bugs. Adding a "did you mean..." kind of output in the output from the pacts for verification response may be possible.