[#5280] Review feedback: do not force save on save-exact

Author: ficocelliguy

workspaces/config/lib/definitions/definitions.js

@@ -1827,9 +1827,6 @@ define('save-exact', {
     version rather than using npm's default semver range operator.
   `,
   flatten (key, obj, flatOptions) {
-    if (obj[key]) {
-      flatOptions.save = true
-    }
     // just call the save-prefix flattener, it reads from obj['save-exact']
     definitions['save-prefix'].flatten('save-prefix', obj, flatOptions)
   },

workspaces/config/test/definitions/definitions.js

@@ -814,11 +814,10 @@ t.test('save-exact', t => {
     'save-exact': true,
     'save-prefix': '~1.2.3',
   }
-  let flat = {}
+  const flat = {}
   mockDefs()['save-exact']
     .flatten('save-exact', { ...obj, 'save-exact': true }, flat)
-  t.strictSame(flat, { savePrefix: '', save: true })
-  flat = {}
+  t.strictSame(flat, { savePrefix: '' })
   mockDefs()['save-exact']
     .flatten('save-exact', { ...obj, 'save-exact': false }, flat)
   t.strictSame(flat, { savePrefix: '~1.2.3' })