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
..
ve.dm.MWTemplateModel.js
ve.dm.MWTemplateParameterModel.js	Code style fix: @return -> @returns	2013-06-17 11:50:24 +01:00
ve.dm.MWTemplatePlaceholderModel.js	Template and content adding	2013-06-18 23:37:44 +00:00
ve.dm.MWTemplateSpecModel.js	Transclusion editor template naming goodness	2013-06-18 18:33:58 -07:00
ve.dm.MWTransclusionContentModel.js
ve.dm.MWTransclusionModel.js	ve.dm.MWTransclusionModel: Don't create undefined normalisation target	2013-06-20 15:09:42 -07:00
ve.dm.MWTransclusionPartModel.js	MWTransclusionModel: Make #getPartById support a param model id	2013-06-18 15:08:44 -07:00