Projects v2

[laander]

Motivation

We're working on a revised Projects model at Timekit that will be more native to the platform. With this also comes an update to our availability engine (successor to FindTime) and Microsoft related endpoints.

Added new endpoints:

// Availability
timekit.fetchAvailability({ ... })

// Projects
timekit.getProjects()
timekit.getProject({ id })
timekit.getHostedProject({ slug })
timekit.getEmbedProject({ id })
timekit.createProject({ ... })
timekit.updateProject({ id, ... })
timekit.deleteProject({ id })
timekit.addProjectResource({ id, ... })
timekit.setProjectResources({ id, resources })
timekit.removeProjectResource({ id, resourceId })

// Account
timekit.getAccounts()
timekit.accountGoogleSignup({ callback }, shouldAutoRedirect)
timekit.accountGoogleSync()
timekit.accountMicrosoftSignup({ callback }, shouldAutoRedirect)
timekit.accountMicrosoftSync()

Side-effects/other

Also improved the DX of the endpoints list in README so it includes a specification of which object properties you can send in the arguments to the methods.

Tests

Updated tests with new endpoints.

Release dependencies

timekit-io/booking-js#176

Who should review it

@Trolzie @vistik

[vistik]

🎱

[Trolzie]

@laander should we consider adding some info about /widgets endpoint to let people know that this is an old endpoint, and they should be using projects instead?

The same question goes to /availability and the old findtime.

[Trolzie]

what about microsoft? does it use the same? should we consider renaming/adding?

[laander]

Ah, good point, I hadn't actually considered that. Let me check in the API routes

[laander]

@Trolzie I have not mentioned in the README on purpose. Although it was public in our API reference at some point, so people don't get any funky ideas and start to use it. If there is a comment about it on http://developers.timekit.io/ , dont you think that would be enough?

[Trolzie]

You are right, docs should be where we do this. I just thought that both internally, plus if people inspect, then it is always nice to see a comment like this when I look at the widget method calls:

// widgets endpoint is no longer encouraged
// use: ´/projects´ instead for future-proofing

I know its a bad example, but you know what i mean :D

[laander]

@Trolzie I like that, good idea, all add some comments in the code 👍

[laander]

@Trolzie I like that, good idea, all add some comments in the code 👍

[Trolzie]

swell @laander I'll wait for the next push 💃

[Trolzie]

lookin good 👾