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

ibm-connections-communities

v1.1.1

Published

An implementation for the IBM Connections Communities API

Downloads

4

Readme

IBM Connections Communities Service

an implementation for the IBM Connections Communities API

Install

$ npm install --save ibm-connections-communities

Usage

After you require community service, you can easily setup the default properties.

const communitiesService = require('ibm-connections-communities');

const defaults = {
  headers: {
    Authorization: 'Basic 12345', // or any other auth method
  },
};

Beside default authorization, this service supports oniyi-http-plugin-credentials and oniyi-http-plugin-format-url-template.

Credentials plugin is used only if plugins.credentials is provided.

Format-url-template is used by default, and it is recommended to use it in combination with credentials plugin.

For more details about plugins usage, please visit:

oniyi-http-plugin-credentials

oniyi-http-plugin-format-url-template

const plugins = {
  credentials: {
    providerName: 'customProvider',
    userRelationProp: 'credentials',
  },
  formatUrlTemplate: {
    valuesMap: {
      authType: {
        basic: 'customAuthType', 
      }
    },
    applyToQueryString: true,
  }
};

const serviceOptions = {
  defaults,
  plugins,
  baseUrl: 'https://base-url.com',
};

const service = communitiesService(serviceOptions.baseUrl, serviceOptions);

If not, please provide you own authorization type directly into the options object. Once service instance is created, you are able to use next methods:

    service.communityMembers

Method comes with three arguments, query, options and callback.

query - valid query parameters for each method can be found in the source code: /lib/methods/*

options - additional options merged into default http request params

service.communityMembers

If you need to retrieve list of all community members, simply provide communityUuid through query object.


const query = {
  communityUuid: 'enter-community-id-here', // not an optional parameter!
  ps: 100, // the default value is 10
};

service.communityMembers(query, {/* request options param */}, (err, response) => {
  const { communityMembers } = response;
  
  // use communityMembers Array to extract metadata about each member.
});

These are the valid query parameters, that can help with sorting/filtering the result:

    -userid
    -email
    -page
    -ps
    -role
    -since
    -sortBy
    -sortOrder

If you need to retrieve a single community member, please provide communityUuid and email/userid through query object.

Warning: When email/userid is provided, all other valid query parameters are ignored!

const query = {
  communityUuid: 'enter-community-id-here',
  userid: '123456', // or email: '[email protected]'
  ps: 100, // this parameter will be ignored
  sortBy: 'name', // this parameter will be ignored as well
};

service.communityMembers(query, {/* request options param */}, (err, communityMember) => {
  // use communityMember Object to extract user's metadata.
});

Running the tests

We are using nock library for recording and mocking HTTP requests. These recordings can be found in test/fixtures/nock-recordings.js file. In order to run them, simply input:

npm run test

If it is necessary to load custom API's and run tests with real-time data, you should to run:

unmocked=true username=basicUser password=basicPassword npm run test

This line of code is saying that tests are not being mocked and will use the real data. Also, please provide valid username and password in order to make a real HTTP request.

License

UNLICENSED © GIS AG