Template talk:Format TemplateData

Refactor

This module should be refactored. It is not maintainable in its current state. Jeblad (talk) 20:05, 1 May 2018 (UTC)

Agree. In fact, I just refactored this to some degree by removing unnecessary imported dependencies. {{3x|p}}ery (talk) 20:20, 1 May 2018 (UTC)

This is a significantly out-of-date fork of de:Modul:TemplateData. There's not much point in refactoring it as it is now; upstream changes should ideally be merged in first. (Which I've been meaning to do, but haven't quite got round to...) I have done a bit of tweaking myself, although nothing very significant. User:GKFX^talk 01:31, 2 May 2018 (UTC)

@GKFX: Are you still doing this? {{3x|p}}ery (talk) 03:05, 23 February 2019 (UTC)

@Pppery: I'm afraid it slipped to the bottom of my to-do list, and I don't think I'm likely to get round to it any time soon. Feel free to do whatever you like to it. User:GKFX^talk 15:05, 1 March 2019 (UTC)

@GKFX: Does that include TfDing the former dependencies I rendered obsolete? {{3x|p}}ery (talk) 19:55, 1 March 2019 (UTC)

@Pppery: Feel free, provided no-one else is using them. Thanks for taking on this module! User:GKFX^talk 10:21, 4 March 2019 (UTC)

Alias bug

Based on Template:Infobox university/doc, this module seems incapable of properly handling aliases. Possibly related to the discussion of @Pppery and @GKFX above. {{u|Sdkb}} ^talk 18:16, 4 June 2021 (UTC)

Ordering

Another bug: This template doesn't seem able to handle ordering. {{u|Sdkb}} ^talk 02:11, 1 September 2021 (UTC)

Incomprehensible error "Defaulted 1 required"

The incomprehensible error "Defaulted 1 required" appears at {{User WP/doc}}. Can someone familiar with this template please:

1. fix the error, if there is an error (or fix the module if the error message is false)
2. explain what the error means, if there was an error
3. add a tracking category so that errors can be tracked down and fixed

Thanks. – Jonesey95 (talk) 03:32, 20 October 2023 (UTC)

I don’t know the inners of the module, but I’d interpret this error message as: a parameter must either have a default value, or be required, not both. Which makes sense, at least in theory – if you expect people to always fill in the parameter, the default value would never be used, so why is it specified? On the other hand, theory and practice are two different things, and people may not fill in the parameter even if you instruct them to do so, in which case that default value does get used. —Tacsipacsi (talk) 15:51, 21 October 2023 (UTC)

I don't think that's an actual error message, more like a reminder note. The default value |1=Example is only used for examples, but should always be filled for actual use of the template. But since being both defaulted and required is a rare situation (as Tacsipacsi perfectly noted), it gets highlited that way. Est. 2021 (talk · contribs) 10:12, 16 December 2023 (UTC)

It is confusing, superfluous and indicating a misunderstood concept or just an error. Both are conflicting and a decision should be made.

There are templates which use an emergency fallback in case of missing mandatory parameter, but that is nothing to be documented and promised.

If default advertised it is optional.

Greetings --PerfektesChaos (talk) 08:59, 15 August 2024 (UTC)

Dark mode troubles

By default, this module sets style="bg:none;color:#000000" on the table. This should be fixed somehow, especially since it causes problems with reading text in dark mode. @PerfektesChaos: maybe you know how. stjn 17:54, 14 August 2024 (UTC)

I am pondering about.

However, “light blue” things will keep light blue things if mentioned anywhere. And “recommended fields are in white rows” are not subject to any change.

Only LINT errors might be avoided, but actually the colour is inherited and Linter should not complain if explicit foreground was set above.

Greetings --PerfektesChaos (talk) 08:43, 15 August 2024 (UTC)