Hello,
Thanks for providing the JS SDK, the decoder works great.
Are there any plans to provide an encoder as well? If so, happy to help test ;)
Thanks,
Matt
Hello,
Thanks for providing the JS SDK, the decoder works great.
Are there any plans to provide an encoder as well? If so, happy to help test ;)
Thanks,
Matt
Sorry for the late reply. There are no immediate plans to support encoding FIT files with the JavaScript SDK. Maybe in the future, but not anytime soon.
The main use-case for the JavaScript SDK is for backend systems written in Node that need to ingest FIT activity files. In this scenario, the FIT files are passed around by device manufacturers to the various 3rd party platforms via APIs and read-only was sufficient.
What is your use-case for needing to encode FIT files?
Thanks for the reply. It's just a weird omission, given that the SDK for most other supported languages (C / C# / C++ / Objective C / Java) include encoder support.
I don't think the specific use-case is important here; if the SDK supports decoding existing FIT data, it would only make sense that it supports encoding as well.
We have been working on an encoder for the JavaScript SDK. We are planning to have it out in early Q1. Follow this thread for updates https://forums.garmin.com/developer/fit-sdk/f/discussion/361529/ability-to-encode-an-activity-using-javascript-sdk/