npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@leisurelink/calendar-client

v3.3.0

Published

## Ambiguity

Downloads

11

Readme

Calendar-client

Ambiguity

There is more than one calendar-client. There is inventory-calendar-client for inventory-calendar, which has a V1 and a V2 published to NPM under the name calendar-client. The V1 is used by Orange, and V2 is used for IH-APP.

This repo will publish calendar-client as a V3 for the GitHub repo calendar-api

Usage

let calendarClient = require('@leisurelink/calendar-client');
let client = calendarClient(keyId, key, baseUrl);

Methods

Constructing

  • let client = calendarClient(keyId, key, baseUrl);
  • keyId: trusted endpoint key id, ex: "my-api/self"
  • key: trusted endpoint key as a Buffer
  • baseUrl: calendar api base URL, for example the dev URL might be https://portal-dev.leisurelink.com

getCalendarById

  • client.getCalendarById(referenceId, lang).then(result => { ... })
  • Used to GET a Calendar object by its referenceId.
  • referenceId: the identifier of the Calendar. This is often the UnitId.
  • lang: sets the language of the request. This is required. For example, en-US
  • Possible response codes:
    • 200 for a success.
    • 400 if the language is not provided or doesn't match the required pattern.
    • 400 if the referenceId is not a standard shortId type identifier.
    • 404 if the calendarId does not have a corresponding document.
    • 500 for any unexpected errors.

putCalendarById

  • client.putCalendarById(referenceId, lang, calendarObject).then(result => { ... })
  • Used to CREATE or REPLACE a Calendar object.
  • referenceId: the identifier of the Calendar. This is often the UnitId.
  • lang: sets the language of the request. This is required. For example, en-US
  • calendarObject: the calendar settings object to store
  • Possible response codes:
    • 200 for a success.
    • 400 if the language is not provided or doesn't match the required pattern.
    • 400 if the referenceId is not a standard shortId type identifier.
    • 400 if unknown properties are passed in.
    • 400 if the calendarType is not a valid Type (NONE, INVENTORY, CONFIRMATION_METHOD)
    • 400 if the defaultConfirmationMethod is not a valid Type (NONE, AVAILABLE, UNAVAILABLE, CALL_AND_REQUEST)
    • 500 for any unexpected errors.

patchCalendarById

  • client.patchCalendarById(referenceId, lang, calendarObject).then(result => { ... })
  • Used to UPDATE a Calendar object.
  • referenceId: the identifier of the Calendar. This is often the UnitId.
  • lang: sets the language of the request. This is required. For example, en-US
  • calendarObject: the calendar settings object to store
  • Possible response codes:
    • 200 for a success
    • 400 if the language is not provided or doesn't match the required pattern
    • 400 if the referenceId is not a standard shortId type id.
    • 400 if unknown properties are passed in.
    • 400 if the calendarType is not a valid Type (NONE, INVENTORY, CONFIRMATION_METHOD)
    • 400 if the defaultConfirmationMethod is not a valid Type (NONE, AVAILABLE, UNAVAILABLE, CALL_AND_REQUEST)
    • 500 for any unexpected errors.

deleteCalendarById

  • client.deleteCalendarById(referenceId, lang).then(result => { ... })
  • Used to DELETE a Calendar object.
  • referenceId: the identifier of the Calendar. This is often the UnitId.
  • lang: sets the language of the request. This is required. For example, en-US
  • Possible response codes:
    • 204 for a success.
    • 400 if the language is not provided or doesn't match the required pattern
    • 400 if the referenceId is not a standard shortId type id.
    • 500 for any unexpected errors.