id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
5182	[PATCH] Conflict system simplification	Upliner	team	"Conflicts in ""visible"" property is quite misleading. I think that user shouldn't decide whether a primitive should be considered as ""visible"" or not. User should have only two choices to delete the primitive(or do nothing if it's already deleted) or to keep it(or undelete it if it have been deleted). Since JOSM now supports proper handling of ""invisible"" objects we can do such simpification. And there are no more need for special purge or undelete command(However, we may need the latter one again if API behavor changes)."	enhancement	closed	normal		Core		fixed		jttt bastiK