Skip to content

C
coopwire-hypothesis
Switch branch/tag
  1. 28 Jun, 2021 6 commits
  3. 24 Jun, 2021 4 commits
  5. 23 Jun, 2021 3 commits
    • Kyle Keating's avatar
      Remove options.defaultValue from hostPageSetting · 0de918ff
      Kyle Keating authored 
      - defaultValue is now handled inside of getConfig so this code is unused.

- hostPageSetting now returns undefined, rather than null, if a value is not found in the config. The undefined value will trigger the defaultValue to take effect in getConfig if a defaultValue is provided.
      0de918ff
    • Kyle Keating's avatar
      Fix default value for showHighlights · da3a3466
      Kyle Keating authored 
      The default was incorrectly set to null because the previous code was setting it to null, however that null value was used to then set it a second time to "always" Part of this refactor is making the code more clear so this logic is explicit. The defaultValue for showHighlight is in fact 'always'
      da3a3466
    • Kyle Keating's avatar
      Remove isBrowserExtension logic from settings.js · 3a9d395a
      Kyle Keating authored 
      nb. This is now handled inside of getConfig()
      3a9d395a
  7. 22 Jun, 2021 2 commits
    • Kyle Keating's avatar
      Pass config name directly to getValue · b208c1e9
      Kyle Keating authored 
      This change fixes the usage of redundant names being expressed in the configDefinitions map.
      b208c1e9
    • Kyle Keating's avatar
      Add `allowInBrowserExt` and `defaultValue` to configDefinitions · d834fefd
      Kyle Keating authored 
      - Logic for `allowInBrowserExt` and `defaultValue` are moved up into getConfig() from various places inside settings. There are no external changes here, but there are a few subtle changes to how a config values work.

  1. Previously if in a browser ext context and  `allowInBrowserEx` was false (default), then the value was was changed to null. This bit of logic was not entirely explicit, but now the logic is that the value will be set to the `defaultValue` if provided or otherwise the value will be omitted entirely. Currently, all values have a `defaultValue` and most of the defaults are null. This ensures things work the same, but also helps bring clarity to what values will be transformed under this condition. Later we can revisit these config values and determine if any don't need a default or simply leave them as is.

  2. The `defaultValue` was previously only used for several fields, but now its set for every field for clarity. It should also be noted that the `defaultValue` will now take precedent over the `coerce` method if settings returns an undefined value for that config key. This is in contrast to how it worked before, but was problematic under some possible circumstances. For example, if a settings value was not found or undefined, and a `defaultValue` was true and the coerce was `toBoolean`, then the value would become false rather than true and that is confusing because the default would not work due to the `coerce` taking precedent. This is now fixed.

- Remove default export from is-browser-extension
      d834fefd
  9. 21 Jun, 2021 14 commits
  11. 17 Jun, 2021 5 commits
  13. 15 Jun, 2021 2 commits
  15. 14 Jun, 2021 4 commits