Hey Krinkle, any chance you can point me to the details of the ForeignResourceManager solution? I wasn't so lucky finding any relevant documentation, and curious what has happened since the RFC log from 2018 where npm/git was the preferred solution.

Surely the sub-class *should* accept a narrower space of values?

Just consider that this is a breaking change, so version number should ideally be bumped to v3.0

I think I've always decided against implementing this as I've learned to consider this a feature rather than a bug. If you don't want the template to be cached you can simply do {{template|}}

Nothing prevents you from making a proper non-alpha 2.0 release (long overdue) with the current code, maintain that to a certain degree and at the same time work on a 3.0 with all the refactoring and ditching compatibility mode.

Yeah, just give @MGChecker or someone else the rights.

May I ask why you are acting like you are still an active member of the team?

The behavior you are describing means the user can smash the return key very early, and will entirely miss the preview that is shown after the input was parsed and formatted.

I don't think it's broken per se. In any case, supporting saving of unparsed values (i.e. ad-hoc parsing) is quite some new feature which would require a lot of work.

@Lydia_Pintscher Why is this an “Epic”? The task's title is way too generic for the given description and what is discussed on http://www.wikidata.org/wiki/Wikidata:Project_chat/Archive/2013/06#minimizing_Item.27s_UI all of which could be done without too much effort but which would arguably require a little more thought and discussion. Way too exaggerated to call these minor design changes a “Redesign Item UI”.

Marked as resolved as pointed out by TheDJ.

@Lydia_Pintscher According to Thiemo, “it should definitely be fixed”. There will always be some non-critical issues for long periods of time in almost any serious software project and that's fine.

@Lydia_Pintscher Please do not just “Decline” a task without an explanation why. This is irritating.

(optional) deduplication of libraries

@Lydia_Pintscher Please elaborate on why this got closed as declined. @Snaterlicious' glossary seems like a good initial effort to this task. So why not build on top of this and commit to cleaning up the mess we've gotten into by not drawing a clear line between Wikidata and the Wikibase software it is based on?

About the mixin, you are right there, my mistake.

To elaborate: The bad thing here is that register() and unregister() have different function signatures than the ones stated in the "super class", resulting in a violation of the class' (or interface's) contract.

Real-world example:

• The data-values/value-view package is defining "jquery.event.special.eachchange.js": ValueView/lib/jquery.event/jquery.event.special.eachchange.js
• Now, recently I needed the same functionality in one of my extensions, so I just copied it over.