https://bugzilla.wikimedia.org/show_bug.cgi?id=43905

--- Comment #6 from Krinkle <[email protected]> ---
(In reply to comment #5)
> (In reply to comment #4)
> > The module wasn't loadable because it isn't registered (this is something
> > your custom startup module needs to do, which it can as it is given the
> > name). So it can't be referred to anywhere unless it is registered by your
> > startup module.
> 
> Then the whole loaderScripts parameter is out of place, or, at the very
> least, mis-designed and poorly documented.
>

I haven't needed to use it often, but this is highly exaggerated and uncalled
for.

>From observation this is what I got, please clarify:

* You don't know much about how ResourceLoader works internally
* You don't understand the purpose of the "loaderScripts" feature.
* You're trying to do something (what exactly?) in an extension that is related
to the words "loader" and "scripts". So you look for documentation, don't find
much but do find "loaderScripts".
* You decide to try and use it, and fail because the way it should be used is
undocumented. It isn't doing what you want and so claim the feature is
mis-designed?

It is not mis-designed, just (arguably) unfortunately named and (yes, most
certainly) undocumented. However the feature itself is very simple and working
just fine if you know what it is for and how to use it. There are no known
bugs, yet (Thanks @mdale).

What you're looking for is not loaderScripts. loaderScripts is a feature to
implement a custom module registry source and/or have dynamically determined
dependencies and/or need to execute certain logic before the first mw.loader
call.

It is not however in anyway related to using "mw.loader.load" and adding a
dependency on a script to be loaded by a url.

If you explain what it is you're trying to do we can point you to a feature
that is relevant to your problem and might actually solve it, too.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to