IMO, if you end up in that situation, you need to invest more effort into figuring out a good solution from the library perspective & maybe even be willing to s

IMO, if you end up in that situation, you need to invest more effort into figuring out a good solution from the library perspective & maybe even be willing to spend the time to implement it - that is the only way you can effect positive change in a more guaranteed fashion towards something that will solve your pain point. Problem is, if you don't come up with a solution, there's no guarantee that the maintainer(s) will be willing to act on it (depending on severity, risk of impact to other users if a change is made with [insert issue], priorities, etc.). If you invest effort towards figuring out a solution/figuring out what is wrong, it helps maintainers dramatically. If it is a persistent pain point, it may be even worthwhile to have a developer devote some time to becoming a maintainer of the project itself, so it derisks your business.