Skip to content

Releases: NordicSemiconductor/pc-nrfconnect-shared

v4.9.5

22 Sep 13:54
051c655
Compare
Choose a tag to compare

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

22 Sep 07:39
9d97769
Compare
Choose a tag to compare

Fixes

  • Fixed app's dependencies in webpack config

v4.9.3

17 Sep 06:21
53b8197
Compare
Choose a tag to compare

Added

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

v4.9.2

16 Sep 13:30
2f01454
Compare
Choose a tag to compare

Fixed

  • Some types

v4.9.1

16 Sep 07:46
0ede397
Compare
Choose a tag to compare

Fixed

v4.9.0

15 Sep 11:14
d3ab482
Compare
Choose a tag to compare

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.

v4.8.19

10 Sep 11:53
5d00665
Compare
Choose a tag to compare

Fixed

  • Version number for 4.8.18 release was wrong in package.json.

v4.8.18

10 Sep 06:33
9211257
Compare
Choose a tag to compare

Updated

  • Added prettier.config.js to existing script npm run lint-init

v4.8.17

09 Sep 08:35
f2d7140
Compare
Choose a tag to compare

Updated

  • New design, device selector: Add PCA number, better alignment for port names, removed wrong line below port names

v4.8.16

08 Sep 11:11
a28068f
Compare
Choose a tag to compare

Added

  • Added support for files written in TypeScript
  • Added Prettier formatting rules to ESLint

Note that apps using this version should add the following entry to their package.json file:

{ "prettier": "./node_modules/pc-nrfconnect-shared/config/prettier.config.js" }

If this isn't added, the Prettier defaults will be used, which differ from our style choices
in a number of ways.

On first run, the linting is likely to fail due to the prevalence of formatting errors.
The majority of these can be fixed automatically, by running npm run lint -- --fix.