adobe/stock-api-libjs

JavaScript implementation of the Stock APIs

Stock API libjs (Deprecated)

This SDK has been deprecated due to lack of maintenance. To use the Stock APIs with JavaScript/Node.js, please call the REST APIs directly.

If you need an archive of this repo, you can pull from an earlier commit.

stock-api-libjs's Issues

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

Consider re-organizing documentation

Hi!

Just wanted to say thank you for the extensive documentation you provide in the README.

My one concern is that it makes the README very long. What does the Stock team think of splitting up usage documentation into its own document?

Also, I noticed your source code is impressively documented at the function level, JSDoc style, I think. That is rad! Maybe we could generate API reference docs based on your extensive function JS docs?

tests fail if you don't have yarn

I only have npm. Is that bad? Is yarn required to run this project?

Perhaps we can either a) update the test script in package.json to call npm run lint instead of yarn run lint or b) make explicit in a new requirements section in the README that yarn is required. Or maybe we can use package.json's engines field for this, too?

CI / CD

It would be nice if the project has some continuous integration support. I think we could probably put something together pretty easily with travis. I am happy to send a PR!

Even more interesting would be continuous deployment. Perhaps based on tags landing in the repo? It would depend on this project's release method/strategy. Perhaps we can talk about releasing, and I can document that process, as a first step? After that we can look at automating.