Following the support question in this forum thread: it would be nice to have site.Translation method to leverage i18n information from the .Translations range.
Enhancement
nekr0z
👍2
All 4 comments
I'm not totally sure about the method name. Since it should behave the same as the current i18n func, maybe we should just name it site.I18n so people don't get other expectations.
bep
on 16 Oct 2020
👍2
Without a capitalized "I", I'd suggest: site.i18n.
martignoni
on 17 Oct 2020
.site.i18n with an alias of .site.T — for full consistency, you know...
nekr0z
on 20 Oct 2020
Without a capitalized "I", I'd suggest: site.i18n.
- As this would be a method on the
Siteinterface, the Go spec forces first character to be uppercase for public/exported methods. site.i18nis technically a function and could be all lowercase (I think), but that is just an alias for.Site.I18n, which is the useful method in this setting, as in:.Sites.First.I18n "foo"
And also, I don't want to fill the Site interface up with aliases.
bep
on 21 Oct 2020
👍1
Was this page helpful?
0 / 5 - 0 ratings
Related issues
arikroc
·
3Comments
geddski
·
3Comments
VoidingWarranties
·
3Comments
tjamet
·
3Comments
sigma
·
3Comments
Most helpful comment
I'm not totally sure about the method name. Since it should behave the same as the current
i18nfunc, maybe we should just name itsite.I18nso people don't get other expectations.