wikimedia/mediawiki-extensions-SyntaxHighlight_GeSHi

Fork 0

mirror of https://gerrit.wikimedia.org/r/mediawiki/extensions/SyntaxHighlight_GeSHi synced 2024-11-15 02:24:07 +00:00

Commit graph

Author	SHA1	Message	Date
Alex Monk	cb61c42dd3	Unbreak VE integration in debug mode The data module was not working properly in debug mode because since Ifeddef8c we've extended FileModule which just tries to use URLs. Change-Id: I822c2e64926a3d6bf1ea53e4fa27bc544ede87d1	2015-07-28 23:59:07 +01:00
Timo Tijhof	1a90245838	ext.geshi.visualEditor: Store languages in the module instead of mw.config Also fixed typo language -> langauge. Change-Id: Ic4bfeb275c479df17e5dd41d5173d9807f6bc1a0	2015-06-25 00:35:20 +00:00
Timo Tijhof	6ba411fe2f	Merge ext.geshi.data and ext.geshi.visualeditor modules Until and unless there is an explicit need (and intent to support) a public interface to use this data elsewhere, there is no need for it to be a separate module. It can be its own class, but at the resource level this data should be considered a JavaScript file. And we don't create separate modules for each file. They are in the same module unless they should be semantically loaded in unrelated page contexts. The module registery is not a javascript class autoloader. There is a global cost to adding more modules to this registry. Change-Id: Ifeddef8cfe00b6c115734f92eceab251a0b75bdb	2015-06-25 00:32:03 +00:00

Author

SHA1

Message

Date

Alex Monk

cb61c42dd3

Unbreak VE integration in debug mode

The data module was not working properly in debug mode because since
Ifeddef8c we've extended FileModule which just tries to use URLs.

Change-Id: I822c2e64926a3d6bf1ea53e4fa27bc544ede87d1

2015-07-28 23:59:07 +01:00

Timo Tijhof

1a90245838

ext.geshi.visualEditor: Store languages in the module instead of mw.config

Also fixed typo language -> langauge.

Change-Id: Ic4bfeb275c479df17e5dd41d5173d9807f6bc1a0

2015-06-25 00:35:20 +00:00

Timo Tijhof

6ba411fe2f

Merge ext.geshi.data and ext.geshi.visualeditor modules

Until and unless there is an explicit need (and intent to support)
a public interface to use this data elsewhere, there is no need
for it to be a separate module.

It can be its own class, but at the resource level this data should
be considered a JavaScript file. And we don't create separate modules
for each file. They are in the same module unless they should be
semantically loaded in unrelated page contexts.

The module registery is not a javascript class autoloader. There
is a global cost to adding more modules to this registry.

Change-Id: Ifeddef8cfe00b6c115734f92eceab251a0b75bdb

2015-06-25 00:32:03 +00:00

3 commits