timrogers / starling-terminal

A tool for viewing your Starling Bank statement from your terminal

Starling Terminal

Starling Terminal lets you view your Starling Bank statement right from your terminal. It's built on the open-source starling-ruby library for the Starling Bank API, and is compatible with Ruby 2.4, Ruby 2.3 and Ruby 2.2.

Usage

Install the gem:

gem install starling_terminal

You'll need to get a personal access token for your Starling account. To get set up, head to the Starling Developers "Get Started" page and then scroll down to the "Personal Access" section for instructions. Set your access token as the environment variable $STARLING_ACCESS_TOKEN.

View your Starling Bank statement from your terminal:

starling

Full documentation is available here.

Tests

The library must pass code checks by RSpec, Rubocop and Reek:

• bundle exec rspec spec: checks the library against automated tests we've written
• bundle exec rubocop: checks the code against established Ruby code style
• bundle exec reek lib: checks the code for "code smells"

As part of our continuous integration (CI) process, we run RSpec, Rubocop and Reek in CircleCI on Ruby 2.4, Ruby 2.3 and Ruby 2.2. Feel free to push up your branch and open a pull request to have Circle test your code.

Contributing

All contributions are welcome - just make a pull request, making sure you include tests and documentation for any public methods, and write a good, informative commit message/pull request body.

Check out CODE_OF_CONDUCT.md to learn about how we can best work together as an open source community to make the Starling Ruby library as good as it can be.

starling-terminal's Issues

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "parser":
  In Gemfile:
    reek (~> 4.7.0) was resolved to 4.7.0, which depends on
      parser (>= 2.4.0.0, < 2.5)

    rubocop (>= 0.49.1, <= 0.62.0) was resolved to 0.52.1, which depends on
      parser (>= 2.4.0.2, < 3.0)

Bundler could not find compatible versions for gem "rspec-core":
  In Gemfile:
    rspec (~> 3.0) was resolved to 3.6.0, which depends on
      rspec-core (~> 3.6.0)

    rspec_junit_formatter (~> 0.2.3) was resolved to 0.2.3, which depends on
      rspec-core (>= 2, != 2.12.0, < 4)

Bundler could not find compatible versions for gem "safe_yaml":
  In Gemfile:
    webmock (~> 3.4.1) was resolved to 3.4.1, which depends on
      crack (>= 0.3.2) was resolved to 0.4.1, which depends on
        safe_yaml (~> 0.9.0)

Could not find gem 'safe_yaml (~> 0.9.0)', which is required by gem 'crack (>= 0.3.2)', in any of the sources.

Bundler could not find compatible versions for gem "virtus":
  In Gemfile:
    reek (~> 4.7.0) was resolved to 4.7.0, which depends on
      codeclimate-engine-rb (~> 0.4.0) was resolved to 0.4.1, which depends on
        virtus (~> 1.0)

Could not find gem 'virtus (~> 1.0)', which is required by gem 'codeclimate-engine-rb (~> 0.4.0)', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "parser":
  In Gemfile:
    reek (~> 4.7.0) was resolved to 4.7.0, which depends on
      parser (>= 2.4.0.0, < 2.5)

    rubocop (>= 0.49.1, <= 0.61.1) was resolved to 0.52.1, which depends on
      parser (>= 2.4.0.2, < 3.0)

Bundler could not find compatible versions for gem "rspec-core":
  In Gemfile:
    rspec (~> 3.0) was resolved to 3.6.0, which depends on
      rspec-core (~> 3.6.0)

    rspec_junit_formatter (~> 0.2.3) was resolved to 0.2.3, which depends on
      rspec-core (>= 2, != 2.12.0, < 4)

Bundler could not find compatible versions for gem "safe_yaml":
  In Gemfile:
    webmock (~> 3.4.1) was resolved to 3.4.1, which depends on
      crack (>= 0.3.2) was resolved to 0.4.1, which depends on
        safe_yaml (~> 0.9.0)

Could not find gem 'safe_yaml (~> 0.9.0)', which is required by gem 'crack (>= 0.3.2)', in any of the sources.

Bundler could not find compatible versions for gem "virtus":
  In Gemfile:
    reek (~> 4.7.0) was resolved to 4.7.0, which depends on
      codeclimate-engine-rb (~> 0.4.0) was resolved to 0.4.1, which depends on
        virtus (~> 1.0)

Could not find gem 'virtus (~> 1.0)', which is required by gem 'codeclimate-engine-rb (~> 0.4.0)', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "parser":
  In Gemfile:
    reek (~> 4.7.0) was resolved to 4.7.0, which depends on
      parser (>= 2.4.0.0, < 2.5)

    rubocop (~> 0.49.0) was resolved to 0.49.1, which depends on
      parser (>= 2.3.3.1, < 3.0)

Bundler could not find compatible versions for gem "rspec-core":
  In Gemfile:
    rspec (~> 3.0) was resolved to 3.6.0, which depends on
      rspec-core (~> 3.6.0)

    rspec_junit_formatter (~> 0.2.3) was resolved to 0.2.3, which depends on
      rspec-core (>= 2, != 2.12.0, < 4)

Bundler could not find compatible versions for gem "safe_yaml":
  In Gemfile:
    webmock (~> 3.4.1) was resolved to 3.4.1, which depends on
      crack (>= 0.3.2) was resolved to 0.4.1, which depends on
        safe_yaml (~> 0.9.0)

Could not find gem 'safe_yaml (~> 0.9.0)', which is required by gem 'crack (>= 0.3.2)', in any of the sources.

Bundler could not find compatible versions for gem "virtus":
  In Gemfile:
    reek (~> 4.7.0) was resolved to 4.7.0, which depends on
      codeclimate-engine-rb (~> 0.4.0) was resolved to 0.4.1, which depends on
        virtus (~> 1.0)

Could not find gem 'virtus (~> 1.0)', which is required by gem 'codeclimate-engine-rb (~> 0.4.0)', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "parser":
  In Gemfile:
    reek (~> 4.7.0) was resolved to 4.7.0, which depends on
      parser (>= 2.4.0.0, < 2.5)

    rubocop (~> 0.49.0) was resolved to 0.49.1, which depends on
      parser (>= 2.3.3.1, < 3.0)

Bundler could not find compatible versions for gem "rspec-core":
  In Gemfile:
    rspec (~> 3.0) was resolved to 3.6.0, which depends on
      rspec-core (~> 3.6.0)

    rspec_junit_formatter (~> 0.2.3) was resolved to 0.2.3, which depends on
      rspec-core (>= 2, != 2.12.0, < 4)

Bundler could not find compatible versions for gem "safe_yaml":
  In Gemfile:
    webmock (~> 3.4.1) was resolved to 3.4.1, which depends on
      crack (>= 0.3.2) was resolved to 0.4.1, which depends on
        safe_yaml (~> 0.9.0)

Could not find gem 'safe_yaml (~> 0.9.0)', which is required by gem 'crack (>= 0.3.2)', in any of the sources.

Bundler could not find compatible versions for gem "virtus":
  In Gemfile:
    reek (~> 4.7.0) was resolved to 4.7.0, which depends on
      codeclimate-engine-rb (~> 0.4.0) was resolved to 0.4.1, which depends on
        virtus (~> 1.0)

Could not find gem 'virtus (~> 1.0)', which is required by gem 'codeclimate-engine-rb (~> 0.4.0)', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

Dependabot can't resolve your Ruby dependency files

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "parser":
  In Gemfile:
    reek (~> 4.7.0) was resolved to 4.7.0, which depends on
      parser (>= 2.4.0.0, < 2.5)

    rubocop (>= 0.49.1, <= 0.62.0) was resolved to 0.52.1, which depends on
      parser (>= 2.4.0.2, < 3.0)

Bundler could not find compatible versions for gem "rspec-core":
  In Gemfile:
    rspec (~> 3.0) was resolved to 3.6.0, which depends on
      rspec-core (~> 3.6.0)

    rspec_junit_formatter (~> 0.2.3) was resolved to 0.2.3, which depends on
      rspec-core (>= 2, != 2.12.0, < 4)

Bundler could not find compatible versions for gem "safe_yaml":
  In Gemfile:
    webmock (~> 3.4.1) was resolved to 3.4.1, which depends on
      crack (>= 0.3.2) was resolved to 0.4.1, which depends on
        safe_yaml (~> 0.9.0)

Could not find gem 'safe_yaml (~> 0.9.0)', which is required by gem 'crack (>= 0.3.2)', in any of the sources.

Bundler could not find compatible versions for gem "virtus":
  In Gemfile:
    reek (~> 4.7.0) was resolved to 4.7.0, which depends on
      codeclimate-engine-rb (~> 0.4.0) was resolved to 0.4.1, which depends on
        virtus (~> 1.0)

Could not find gem 'virtus (~> 1.0)', which is required by gem 'codeclimate-engine-rb (~> 0.4.0)', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.