Re: Is there any reason to set the default reverse relationship name in the current format?

It helped a lot. Thank you! Jeonghun Kim 2021년 8월 9일 월요일 오후 7시 19분 21초 UTC+9에 Adam Johnson님이 작성: > Ruby on Rails uses "correct" plural forms in code. But in order to do this > it contains a special library to pluralize words correctly, e.g. octopus -> > octopuses. And naturally that strategy

Re: Is there any reason to set the default reverse relationship name in the current format?

Ruby on Rails uses "correct" plural forms in code. But in order to do this it contains a special library to pluralize words correctly, e.g. octopus -> octopuses. And naturally that strategy requires per-language and per-word knowledge, and can go wrong when trying to use non-english words. Rather

Is there any reason to set the default reverse relationship name in the current format?

Hi, Django's default reverse relationship name is a model name followed by a _set suffix. In terms of readability, depending on the type of relationship used, I think it would be good to make the default reverse relationship name in the singular or plural form of the model name. Is there any