tastytrade 0.2.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: b4642b3bfaeb7906f2733b1da34c2bafea177177fb6670f2271b50b720673236
+  data.tar.gz: d65a41b22c7eba317269b454e38188b1e19c504726771d140d72653aa7e7c617
+SHA512:
+  metadata.gz: 7dd6ac7a321ed6d7c6b9519f82988029f5e49515acfff9583d22bba99b2da2ab61666e9054ee232a71afdd3179bcc97c1765e071081722160251ef207340f2d2
+  data.tar.gz: 20b1acf6efba69d72bee9448c39825178701a0e4a20be5de813f1607860fa201b5ed68d2269b2d465fa085bc817d7ffa0ff7f7d89dd68849d197f18463841d51

data/.claude/commands/release-pr.md

@@ -0,0 +1,108 @@
+# release-pr
+
+Create a release PR following Ruby gem best practices.
+
+## Steps to Execute
+
+1. **Determine Version Bump**
+   - Review the CHANGELOG.md "Unreleased" section
+   - Determine the appropriate version bump based on Semantic Versioning:
+     - MAJOR (x.0.0): Breaking changes
+     - MINOR (0.x.0): New features, backward compatible
+     - PATCH (0.0.x): Bug fixes only
+   - Ask the user to confirm the version if unclear
+
+2. **Create Release Branch**
+   ```bash
+   git checkout -b release/v<VERSION>
+   ```
+
+3. **Update Version**
+   - Edit `lib/tastytrade/version.rb` to bump the version number
+
+4. **Update ROADMAP.md**
+   - Review the CHANGELOG.md "Unreleased" section for completed items
+   - Find corresponding items in ROADMAP.md and mark them as completed:
+     - Change `- [ ]` to `- [x]` for completed items
+   - Look for items in all phases, not just Phase 1
+   - If an item mentions a GitHub issue number, include "(closes #X)" after marking complete
+
+5. **Update CHANGELOG.md**
+   - Move all entries from "Unreleased" to a new version section with today's date
+   - Format: `## [X.Y.Z] - YYYY-MM-DD`
+   - Create a new empty "Unreleased" section at the top with all subsections:
+     ```markdown
+     ## [Unreleased]
+     
+     ### Added
+     - Nothing yet
+     
+     ### Changed
+     - Nothing yet
+     
+     ### Deprecated
+     - Nothing yet
+     
+     ### Removed
+     - Nothing yet
+     
+     ### Fixed
+     - Nothing yet
+     
+     ### Security
+     - Nothing yet
+     ```
+
+6. **Commit Changes**
+   ```bash
+   git add lib/tastytrade/version.rb CHANGELOG.md ROADMAP.md
+   git commit -m "Release v<VERSION>"
+   ```
+
+7. **Push Branch**
+   ```bash
+   git push -u origin release/v<VERSION>
+   ```
+
+8. **Create Pull Request**
+   ```bash
+   gh pr create --title "Release v<VERSION>" --body "## Release v<VERSION>
+
+   This PR prepares the release of version <VERSION>.
+
+   ### Changes
+   - Bumped version to <VERSION>
+   - Updated CHANGELOG.md with release date
+   - Updated ROADMAP.md to mark completed items
+   
+   ### Release Checklist
+   - [ ] Version number is correct
+   - [ ] CHANGELOG.md is updated with all changes
+   - [ ] ROADMAP.md has completed items marked
+   - [ ] All tests pass
+   - [ ] RuboCop reports no offenses
+   
+   ### Post-Merge Steps
+   After merging this PR:
+   1. \`git checkout main && git pull\`
+   2. \`bundle exec rake release\`
+   
+   Note: The rake release command will automatically create and push the git tag v<VERSION>"
+   ```
+
+## Important Notes
+
+- Do NOT run `rake release` as part of the PR - this happens after merge
+- Ensure all tests pass before creating the PR
+- Run RuboCop to ensure code quality
+- The version in the PR title and body should NOT include the 'v' prefix (e.g., "0.2.0" not "v0.2.0")
+- The rake release command will automatically create the git tag with 'v' prefix (e.g., "v0.2.0")
+- You need a RubyGems.org account to run rake release
+
+## Example
+
+For a minor version bump from 0.1.0 to 0.2.0:
+- Branch name: `release/v0.2.0`
+- Commit message: `Release v0.2.0`
+- PR title: `Release v0.2.0`
+- Git tag (after merge): `v0.2.0`

data/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,29 @@
+---
+name: Feature request
+about: Suggest a new feature for the SDK
+title: '[FEATURE] '
+labels: enhancement
+assignees: ''
+---
+
+## Feature Description
+A clear and concise description of what you want to happen.
+
+## Use Case
+Describe the use case or problem this feature would solve.
+
+## Proposed Solution
+Describe how you'd like this feature to work.
+
+## Alternatives Considered
+Describe any alternative solutions or features you've considered.
+
+## Roadmap Phase
+Which phase of the roadmap does this belong to?
+- [ ] Phase 1: Core SDK Foundation
+- [ ] Phase 2: Advanced SDK Features
+- [ ] Phase 3: CLI Integration
+- [ ] Phase 4: Advanced Features & Polish
+
+## Additional Context
+Add any other context or screenshots about the feature request here.

data/.github/ISSUE_TEMPLATE/roadmap_task.md

@@ -0,0 +1,34 @@
+---
+name: Roadmap Task
+about: Track implementation of a roadmap item
+title: '[ROADMAP] '
+labels: roadmap
+assignees: ''
+---
+
+## Task Description
+Brief description of the roadmap task to implement.
+
+## Roadmap Reference
+Link to the specific item in ROADMAP.md this implements.
+
+## Phase
+- [ ] Phase 1: Core SDK Foundation
+- [ ] Phase 2: Advanced SDK Features  
+- [ ] Phase 3: CLI Integration
+- [ ] Phase 4: Advanced Features & Polish
+
+## Implementation Details
+Detailed technical approach for implementing this feature.
+
+## Acceptance Criteria
+- [ ] Implementation complete
+- [ ] Tests written and passing
+- [ ] Documentation updated
+- [ ] Code reviewed
+
+## Dependencies
+List any other roadmap items that must be completed first.
+
+## Notes
+Any additional implementation notes or considerations.

data/.github/dependabot.yml

@@ -0,0 +1,11 @@
+version: 2
+updates:
+  - package-ecosystem: "bundler"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 10
+    groups:
+      dependencies:
+        patterns:
+          - "*"

data/.github/workflows/main.yml

@@ -0,0 +1,75 @@
+name: CI
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+permissions:
+  contents: read
+
+jobs:
+  scan_ruby:
+    runs-on: ubuntu-latest
+    
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v4
+    
+    - name: Set up Ruby
+      uses: ruby/setup-ruby@v1
+      with:
+        ruby-version: .ruby-version
+        bundler-cache: true
+    
+    - name: Scan for security vulnerabilities
+      run: |
+        gem install bundler-audit
+        bundle-audit check --update
+
+  lint:
+    runs-on: ubuntu-latest
+    
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v4
+    
+    - name: Set up Ruby
+      uses: ruby/setup-ruby@v1
+      with:
+        ruby-version: .ruby-version
+        bundler-cache: true
+    
+    - name: Lint code for consistent style
+      run: bundle exec rubocop
+
+  test:
+    runs-on: ubuntu-latest
+    
+    strategy:
+      fail-fast: false
+      matrix:
+        ruby-version:
+          - '3.2'
+          - '3.3'
+          - '3.4'
+    
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v4
+    
+    - name: Set up Ruby
+      uses: ruby/setup-ruby@v1
+      with:
+        ruby-version: ${{ matrix.ruby-version }}
+        bundler-cache: true
+    
+    - name: Run tests
+      run: bundle exec rake spec
+    
+    - name: Upload coverage reports
+      uses: codecov/codecov-action@v4
+      if: matrix.ruby-version == '3.3'
+      with:
+        fail_ci_if_error: false

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,101 @@
+AllCops:
+  DisabledByDefault: true
+  TargetRubyVersion: 3.2
+  SuggestExtensions: false
+  Exclude:
+    - 'bin/*'
+    - 'vendor/**/*'
+    - 'tmp/**/*'
+
+# Style Rules
+Style/HashSyntax:
+  Enabled: true
+
+Style/StringLiterals:
+  Enabled: true
+  EnforcedStyle: double_quotes
+
+Style/StringLiteralsInInterpolation:
+  Enabled: true
+  EnforcedStyle: double_quotes
+
+Style/MultilineIfThen:
+  Enabled: true
+
+Style/MethodDefParentheses:
+  Enabled: true
+
+Style/RedundantReturn:
+  Enabled: true
+
+Style/RedundantSelf:
+  Enabled: true
+
+Style/RedundantInterpolation:
+  Enabled: true
+
+# Layout Rules
+Layout/LineLength:
+  Enabled: true
+  Max: 120
+
+Layout/IndentationWidth:
+  Enabled: true
+
+Layout/IndentationStyle:
+  Enabled: true
+
+Layout/EmptyLines:
+  Enabled: true
+
+Layout/TrailingEmptyLines:
+  Enabled: true
+
+Layout/TrailingWhitespace:
+  Enabled: true
+
+Layout/SpaceBeforeBlockBraces:
+  Enabled: true
+
+Layout/SpaceInsideBlockBraces:
+  Enabled: true
+
+Layout/SpaceInsideHashLiteralBraces:
+  Enabled: true
+
+Layout/SpaceInsideArrayLiteralBrackets:
+  Enabled: true
+
+Layout/SpaceInsideParens:
+  Enabled: true
+
+Layout/SpaceAroundOperators:
+  Enabled: true
+
+Layout/CaseIndentation:
+  Enabled: true
+
+Layout/EndAlignment:
+  Enabled: true
+  EnforcedStyleAlignWith: variable
+
+Layout/ElseAlignment:
+  Enabled: true
+
+Layout/EmptyLinesAroundClassBody:
+  Enabled: true
+
+Layout/EmptyLinesAroundModuleBody:
+  Enabled: true
+
+Layout/EmptyLinesAroundMethodBody:
+  Enabled: true
+
+Layout/FirstHashElementIndentation:
+  Enabled: true
+
+Layout/HashAlignment:
+  Enabled: true
+
+Layout/MultilineMethodCallIndentation:
+  Enabled: true

data/.ruby-version

@@ -0,0 +1 @@
+3.4.5

data/CHANGELOG.md

@@ -0,0 +1,100 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+### Added
+- Nothing yet
+
+### Changed
+- Nothing yet
+
+### Deprecated
+- Nothing yet
+
+### Removed
+- Nothing yet
+
+### Fixed
+- Nothing yet
+
+### Security
+- Nothing yet
+
+## [0.2.0] - 2025-08-01
+
+### Added
+- Initial gem structure with professional Ruby gem scaffold
+- Basic configuration files (RuboCop, RSpec, GitHub Actions)
+- Development tooling setup
+  - RSpec test framework with SimpleCov coverage reporting
+  - RuboCop linter with custom configuration
+  - GitHub Actions CI for multi-OS and multi-Ruby testing
+- HTTP client infrastructure (#16, #17, #19)
+  - Faraday as HTTP client with retry middleware
+  - RESTful methods (GET, POST, PUT, DELETE)
+  - Automatic retry for transient failures (429, 503, 504)
+  - Configurable timeout settings
+  - Production/sandbox environment support
+- Comprehensive error handling framework (#17)
+  - InvalidCredentialsError for authentication failures
+  - SessionExpiredError for expired sessions
+  - TokenRefreshError for refresh failures
+  - NetworkTimeoutError for connection timeouts
+  - Unified error response parsing
+- Session management with authentication (#1-5)
+  - Basic session class with login/logout
+  - Remember token authentication support
+  - Session expiration tracking and automatic refresh
+  - Secure credential storage using system keyring
+  - Session validation and error handling
+- Account models and data structures (#20)
+  - Account model with proper data parsing
+  - AccountBalance model with BigDecimal precision for monetary values
+  - CurrentPosition model for position tracking with P&L calculations
+  - Support for options, equities, and futures positions
+- CLI foundation with interactive mode (#23, #24)
+  - Core CLI structure using Thor
+  - `login` command with --remember and --test flags
+  - `logout` command with session cleanup
+  - `status` command to check session status and expiration
+  - `refresh` command to refresh session using remember token
+  - `accounts` command to list all accounts
+  - `select` command to choose active account
+  - `balance` command with table formatting and --all flag
+  - Interactive menu-driven interface
+  - Vim-style navigation (j/k for up/down, q/ESC to exit)
+  - Number key shortcuts for menu selection
+  - Automatic entry into interactive mode after login
+- CLI helper utilities
+  - Colored output helpers (error, warning, success, info)
+  - Currency formatting with thousand separators
+  - TTY::Table integration for data display
+  - Pastel color support
+- Configuration management
+  - YAML-based configuration file (~/.config/tastytrade/config.yml)
+  - Environment persistence (production/sandbox)
+  - Current account selection persistence
+  - Safe config file handling with error recovery
+- Security features
+  - MIT License
+  - Code of Conduct
+  - Security policy documentation
+  - Keyring integration for secure credential storage
+
+### Changed
+- Account.get_balances now returns AccountBalance object instead of raw hash
+- Account.get_positions now returns array of CurrentPosition objects instead of raw hashes
+- CLI menus now use consistent vim-style navigation with extracted helper method
+- Updated release-pr Claude Code command to include ROADMAP.md updates in release process
+- Removed MFA requirement for RubyGems.org publishing
+- Updated release-pr command to reflect that rake release auto-creates git tags
+
+### Fixed
+- Account data parsing from API response (#25)
+- "Failed to load current account" error in balance view by implementing account caching
+- TTY::Table rendering in non-TTY environments with fallback formatting

data/CLAUDE.md

@@ -0,0 +1,78 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Common Development Tasks
+
+### Running Tests
+```bash
+bundle exec rake spec         # Run all tests
+bundle exec rspec spec/path   # Run specific test file
+```
+
+### Code Quality
+```bash
+bundle exec rake rubocop      # Run linter
+bundle exec rubocop -a        # Auto-fix linting issues
+```
+
+### Development Console
+```bash
+bin/console                   # Interactive Ruby console with gem loaded
+```
+
+### Building and Installing Locally
+```bash
+bundle exec rake build        # Build gem to pkg/
+bundle exec rake install      # Install gem locally
+```
+
+### Release Process
+```bash
+bin/release                   # Interactive release script
+# OR manually:
+# 1. Update version in lib/tastytrade/version.rb
+# 2. Update CHANGELOG.md
+# 3. bundle exec rake release
+```
+
+## Project Structure
+
+```
+tastytrade/
+├── lib/
+│   └── tastytrade/          # Main gem code
+│       └── version.rb       # Version constant
+├── spec/                    # RSpec tests
+├── bin/                     # Executable scripts
+│   ├── console             # Development console
+│   ├── setup               # Setup script
+│   └── release             # Release automation
+├── docs/                    # Additional documentation
+└── .github/workflows/       # CI/CD configuration
+```
+
+## Architecture Notes
+
+This is a Ruby gem scaffold with professional tooling setup:
+- RSpec for testing with SimpleCov for coverage
+- RuboCop for code style enforcement
+- GitHub Actions for multi-OS and multi-Ruby CI
+- Security policy and contribution guidelines
+- Professional README with badges and clear sections
+
+## Key Development Patterns
+
+1. **Version Management**: Version is defined in `lib/tastytrade/version.rb`
+2. **Testing**: Mirror directory structure in spec/, use descriptive test names
+3. **Documentation**: Use YARD format for method documentation
+4. **Error Handling**: Raise specific error classes, not generic exceptions
+5. **Dependencies**: Keep runtime dependencies minimal, use development dependencies liberally
+
+## Gem-Specific Configurations
+
+- Ruby 3.2.0+ required
+- RuboCop configured with custom rules in `.rubocop.yml`
+- RSpec configured in `.rspec` and `spec/spec_helper.rb`
+- Git-based file inclusion in gemspec
+- MFA required for RubyGems.org pushes

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,81 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at 58859899+ryanhamamura@users.noreply.github.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.