0
I Use This!
Inactive

Commits : Listings

Analyzed 1 day ago. based on code collected 1 day ago.
Jan 31, 2025 — Jan 31, 2026
Commit Message Contributor Files Modified Lines Added Lines Removed Code Location Date
Added support for import vs. syncing of data in Data provider - and implemented on FitbitAccount More... about 12 years ago
Merge pull request #21 from jdjkelly/staging More... about 12 years ago
Merge pull request #20 from jdjkelly/feature/data_provider_api More... about 12 years ago
Removed sleeps for release More... about 12 years ago
Updated readme ideas More... about 12 years ago
Simplified Fitbit API call for weights - we'll have to handle this later More... about 12 years ago
Restructured WithingsAccount to match FitbitAccount More... about 12 years ago
Added data provider example support to WithingsAccount More... about 12 years ago
Reset data_providers_for after each spec - that way the specs can run for each individual API provider More... about 12 years ago
Clean up gemfile - organize etc More... about 12 years ago
Tweaked name of sleep ends after start validator, made private, and added a few matchers to sleep spec More... about 12 years ago
Added support for Units to convert to their existing unit - in case we don't know the initial unit More... about 12 years ago
Added /concerns to autoloader and updated i18n config to get rid of deprecation error More... about 12 years ago
Syntax change for Ruby hashes More... about 12 years ago
Fixed bad commit More... about 12 years ago
CircleCI bombs on these without requiring them More... about 12 years ago
New DataProvider API strategy involves using DataProvider as a Concern-style module, and introducing the data_provider_for model DSL. We can now include the Concern and use data_provider_for :x, :y, :z in our API provider classes. This will automatically execute matching methods to those symbols on create, otherwise raising a NotImplemented exception. This is the underpinning for making API additions fast, and consistent. In the future, we should only have to define the internals of each symboled type of resource provided to data_provider_for More... about 12 years ago
Added new Exception to Exceptions class to support DataProvider API strategy More... about 12 years ago
Rewrote Guardfile line to remove regex inside string matcher - this was producing deprecation warnings More... about 12 years ago
Removed unnecessary config in spec_helper - we aren't using fixtures More... about 12 years ago
Merge pull request #18 from jdjkelly/staging More... about 12 years ago
Improved homepage design More... about 12 years ago
Fix broken JS More... about 12 years ago
Capture errors from provider sync More... about 12 years ago
Moved sync to user#show. Fundamentally, I'm unsure how to implement this intelligently. Maybe it really should just be part of the login process? Done in parallel, this could be reasonably efficient. The trouble with this is that Warden's after_authentication only happens once the user actually signs in - but if it's a cookied or tokened request, how do we know? More... about 12 years ago
Added exceptions class More... about 12 years ago
Visual hotfixes for footer More... about 12 years ago
Merge branch 'staging' More... about 12 years ago
Visual improvements to footer More... about 12 years ago
Hotfix for issue with javascript More... about 12 years ago