fitbit-sdk-types

Fitbit SDK Types ✔

Add types to your Fitbit CLI project and work safely with TypeScript preventing you of doing stupid mistakes.

⚙ How to use in your app project

1. First, create your Fitbit CLI project following the official instructions at https://dev.fitbit.com/build/guides/command-line-interface/.

2. Then, from that project root, run npx fitbit-sdk-types install. Also you acn use the following optional flags to customize your TypeScript and Visual Studio Code integrations.

   • --vscode: add a few tweaks to integrate with Visual Studio Code

     • Background tasks

     • Problems report

   • --migrate: rename all the .js files to .ts.

3. Take a look at the FAQ.

Benefits of using types

Discoverability

Know what is available to build your ideas right from your code.

Enumerated and strict string literals

Also in JSX for settings

Integrated with the Fitbit CLI build process

It is fully integrated within the Fitbit CLI build process that already uses TypeScript. With this approach you are just extending its knowledge about what can you use and how.

So if your code is not ok, then it won't build. That way it will prevent you from wasting a lot of time with typos, undefined functions and trivial bugs, letting you focus on what really matters.

Code error, so the build process fails

Examples

You can see a ton of official examples working as tests right here, under the ./test-code-samples path.

Gotchas

Be strict...

• 🧐 To have a full type experience: add the strict mode to your tsconfig.json:

{
	"compilerOptions": {
		"strict": true
	}
}

... Or not

You can always place // @ts-ignore right above that line of code that you know that should work, and probably needs to have it's typings fixed.

SDK Support

Only the latest SDK version is supported. Also don't expect this project version to match the official SDK version.

Contributing

❗ Open an issue

If you have a question, suggestion or bug report, don't be shy and open an issue 🎈.

💪 Make a PR

1. The use cases you think that must be covered, under a meaningful section inside test-code-samples/.
2. The type definition in the appropiate types/ file.
3. If possible, a link to the official documentation or community forum thread.