Guidance on allowing opinion to change when guessing types

[Westie]

Hi all

I'm wanting to change some functionality within a project that we're working on to better fit with the opinions that we as a team have with regards to naming conventions.

At present the code sort of allows types to be guessed - but it does it in about only a third of the cases.

I want to make it so that we're able to do this in all the cases, can I get some hints as to what the most standards compliant manner for this project for adding these guessers would be?

(See further, relation type inversion guessers, it's all hidden with protected methods)

Would I need to add these via the Server::serving method, or is there a much better way of doing this?

I'm not asking for others to do the work, I'm more than happy to do it myself

[lindyhopchris]

Hi! Thanks for opening this issue. I think I need more information as I don't fully understand everything you've raised.

At present the code sort of allows types to be guessed - but it does it in about only a third of the cases.

What do you mean by "only a third of the cases"? The guessing is consistent throughout the package, so need this unpacked a bit to understand what you mean.

Overall, I would support overriding of the "guessers" as you've put them... but you'd need to do the work as I can't really prioritise this over other things.

I think a starting point would be for you to identify all the bits in the code that you think need overriding. Then we could agree an approach for the PR to take. Think that would be sensible before you write any code.