Sha256: bb7c51b3e0f662f7566278724af0f705d0d42455cc3b0977ce59bc3aef83d3aa
Contents?: true
Size: 1.51 KB
Versions: 1
Compression:
Stored size: 1.51 KB
Contents
TODO: UPDATE THIS! ## Development After checking out the repo, run `bin/setup` to install dependencies. You can also run `bin/console` for an interactive prompt that will allow you to experiment. To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org). ## Running tests The gem test suite can be run in two modes. By default, it runs against the live sandbox environment, creating items on the fly and calling various API endpoints for them. For this to work you'll need real `client_id` and `secret` from your Plaid dashboard. Create a file named `.env` based on `.env.sample` which is provided: ```text PLAID_RUBY_CLIENT_ID=the_real_client_id PLAID_RUBY_SECRET=the_real_secret ``` This file will be loaded during the tests. ## Contributing 1. Make one or more atomic commits, and ensure that each commit has a descriptive commit message. Commit messages should be line wrapped at 72 characters. 2. Make sure that there are tests for the code you wrote. 3. Make sure that you've documented all public methods using [TomDoc](http://tomdoc.org/). 4. Run tests (in both modes, see above) and address any errors. Preferably, fix commits in place using `git rebase` or `git commit --amend` to make the changes easier to review. 5. Open a pull request.
Version data entries
1 entries across 1 versions & 1 rubygems
Version | Path |
---|---|
plaid-14.0.0.beta.1 | CONTRIBUTING.md |