Timo Tijhof 8f9093ea07 ve.dm.MWTransclusionModel: Don't create undefined normalisation target ... The API gives us normalisation information about all titles, including titles of which it couldn't provide any template data. Spec storage should only have properties with valid values (has property means to have a valid value, like database). The absence of this check was causing it to turn this: { pages: { 'Template:Unsigned': { params: { .. } } }, normalised: [ { from: 'foo bar', to: 'Foo_bar' }, { from: 'template: unsigned', to: 'Template:Unsigned' } ] } into: { pages: { 'foo bar': undefined }, normalised: [ { from: 'foo bar', to: 'Foo_bar' } ] } Bug: 49493 Change-Id: I0b661744d0388345561897c9631f15e691737031		2013-06-20 15:09:42 -07:00
..
jquery	Merge "Implement new browser compatibility checks"	2013-06-05 12:32:56 +00:00
oojs	oojs: Integrate with OOJS v1.0.0	2013-06-06 17:29:55 +02:00
qunit
rangy	Convert from DOS line endings (CRLF) to Unix ones (LF)	2013-05-25 23:51:21 +02:00
unicodejs	splitClusters uses Grapheme Cluster Boundary rules	2013-06-16 21:46:02 +01:00
ve	ve.dm.MWTransclusionModel: Don't create undefined normalisation target	2013-06-20 15:09:42 -07:00