Thiemo Kreuz 9e74e2f352 Ignore default values as not being valuable as well ... This check makes sure the user doesn't loose work when clicking the back button. I would like to argue that neither of these values is valuable enough to block the user with a confirmation dialog: * Literally nothing is lost when the input is empty. * The auto-value is only temporarily lost, but will automatically be restored when the user decides to add the template back. The input field is pre-filled with this value. * The default value doesn't need to be manually entered. It will show up anyway when the parameter is missing. There is a rare edge-case, but it is not really relevant in this situation. Some templates allow to override a default value with the empty string. This will be considered irrelevant by this code. However, this was already happening before and doesn't change with this patch. The only edge-case where this patch makes a difference is if a parameter is marked as required or suggested, is documented to have a default value, _and_ the template allows to override it with an empty string. But this combination is rather crazy, if not bogus, and not worth considering here, I believe. Bug: T274551 Change-Id: Ib176a82844335c3d4dd5b720d335ec28245e1637		2021-08-09 10:28:09 +00:00
..
annotations
metaitems
models	Ignore default values as not being valuable as well	2021-08-09 10:28:09 +00:00
nodes	Merge "Rewrite MWTransclusionNode.isSingleTemplate for readability"	2021-07-01 11:21:44 +00:00
.eslintrc.json
ve.dm.MWWikitextSurface.js
ve.dm.MWWikitextSurfaceFragment.js