Move to preconfigured Resin-SDK

[pimterry]

No description provided.

[jviotti]

I approved, though I think you need to rebuild the CoffeeScript.

[pimterry]

Ah, thanks. Now fixed, I'll merge once the build passes.

[Page-]

So I've seen a load of these PRs pop up, and it seems that this special version of the SDK is being used everywhere? Is there ever a case when we would use the "standard" SDK? In general does it make more sense to have the "standard" SDK match the standard usage instead of the more uncommon usage, or at least have it default to the standard usage (in order to make the common case easier for everyone)?

[emirotin]

The SDK itself is a factory. This version is an instantiated version of the factory, with all the params passed in. The other use-case is the browser (UI / dashboard) where we (will) initialize it a bit differently (specifically by first querying the API and then passing the obtained params to the SDK). There are plans to eventually encapsulate those params in the same `-preconfigured` module, too, but for now it's just a thin wrapper for Node-only projects.

…

On Tue, Jan 17, 2017 at 12:36 AM, Page- ***@***.***> wrote: So I've seen a load of these PRs pop up, and it seems that this special version of the SDK is being used everywhere? Is there ever a case when we would use the "standard" SDK? In general does it make more sense to have the "standard" SDK match the standard usage instead of the more uncommon usage, or at least have it default to the standard usage (in order to make the common case easier for everyone)? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAgGCMT6M6ZyI32_LIyFoWyk9CnfAlbkks5rS-LIgaJpZM4LjCa9> .

-- Eugene Mirotin Senior Frontend Engineer site: Resin.io <https://resin.io/>, twitter: @resin_io <https://twitter.com/resin_io>