v4.9.8

4.9.8

Updated

• Updated logic to decide which network interface to use to generate client id

v4.10.0

Added

• Enable showing an own icon and links on the About pane for USB connected devices.

Steps to upgrade when using this package

• This version does introduce a first file in shared that is converted from JavaScript to TypeScript: deviceInfo. While most is already prepared for that, the webpack.config.js in the launcher still needs two adjustments to work with this: The lines 39 and 69 needs to be changed, so that webpack does not only pick up files with the ending .jsx? but also .tsx?. Apps, on the other hand, do not need to be changed for this.

v4.9.7

v4.9.7

Updated

• Updated how client is generated for usage statistics

v4.9.6

Added

• Added optional range.decimals to be validated for NumberInlineInput
• Updated index.d.ts with rangeShape

v4.9.5

Fixed

• More type enhancements:
  • Correct systemReport signature
  • Limit array types to readonly where possible
  • Do not use void as a callback return value
• Make linting fail if the type check fails
• Remove conflicting ESLint rule 'quotes'
• Lint all JavaScript files in this project, not just the ones in src/

v4.9.4

Fixes

• Fixed app's dependencies in webpack config

v4.9.3

Added

• Added focus-visible dependency and disabled focus styles when clicked

v4.9.2

Fixed

• Some types

v4.9.1

Fixed

• Relax ESLint rule regarding @ts-ignore comments

v4.9.0

Added

• Default tsconfig.json for other projects to use
• Additional checks during linting:
  • Check for a tsconfig.json if the project uses TypeScript (if there are
    any files with the endings .ts or .tsx)
  • Run tsc --noEmit if there is a tsconfig.json to check the TypeScript
    types

Fixed

• Type error in bleChannels

Steps to upgrade when using this package

• If you want to use the settings from config/tsconfig.json in a
  TypeScript project, then put this into a tsconfig.json in the
  root of your project:

  {
    "extends": "./node_modules/pc-nrfconnect-shared/config/tsconfig.json",
  }
  

  Please note that tsconfig.json is not used for the compilation of your
  project. We use the TypeScript transform plugin of babel for compilation and
  that does not use the settings from
  tsconfig.json.
  But the settings in tsconfig.json are useful nonetheless, because they
  respected by many IDEs and editors as well as when you run tsc.

  If you want to override any settings from the default tsconfig.json you
  are free to do so. We put strict on true in there because that is what
  we aim for but you may want to relax that a bit when transitioning existing
  projects.