eg prefix for extension config variables

Jump to: navigation, search

It was in there for three years; see r70755 and comments. That's why you've seen other extensions do it.

Reach Out to the Truth15:47, 5 December 2011

I don't quite understand, so it's no longer best practice to use it for extensions? Why not?

Danwe16:00, 5 December 2011

It's not that it's not best practice, it's that it snuck into the coding conventions under the radar, people read it as gospel, and now we've got $eg and ef all over the place when nobody ever really recommended it to begin with.

You can call your config globals $the_most_awsome_variable_in_the_world if you really wanted to, it doesn't matter in a practical sense.

^demon16:21, 5 December 2011

So what would be the way to get it back into coding conventions in a proper way? Doesn't seem that bad and more consistency in extension development wouldn't harm I guess.

Danwe17:51, 5 December 2011

Extensions should just use $wg, like core.

^demon22:04, 5 December 2011
 
 
 
 
Personal tools

Variants
Actions
Navigation
Support
Download
Development
Communication
Toolbox