Importing of kresus.json should not import setting if the setting does not have a default value
A user did this :
- he created a kresus based on the 'master' branch (cloned + manual build)
- exported the database including
budgetDisplayNoThreshold
setting - installed kresus directly from npm (0.13.3)
- imported the databas (with setting
budgetDisplayNoThreshold
)
On launching the client an assert is raised as budgetDisplayNoThreshold
(among others) is not known by the client.
We should not import settings in the database which are not known (no DefaultSetting)