Giter VIP home page Giter VIP logo

hopper's Introduction

holman

holman

holman

gem install holman

gem install holman

gem install holman

holman

holman

holman

hopper's People

Contributors

holman avatar kl-7 avatar remi avatar winescout avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

hopper's Issues

Standardize Test Setups

Now that probe tests have shaken out a little bit, let's effectively remove most of the setup block. Add a helper (maybe in the fixture call) that:

  • Initializes a @project
  • Initializes a @probe (based on current file's target probe, if possible)
  • Stubs out the head revision

Repo interface

Right now we tuck repo in as a method on a Source. This is horrible because it's already getting crowded- methods on GitHub (the Source) are getting intermixed with Git operations.

On top of this, when we start using other things like Subversion repos, we can't do things like we're currently doing in Probes- i.e., Rugged-specific tree walking and blob access.

We need a Repo (or Repository) model that can model our on-disk data. We can put all of our generalized file access here. I haven't thought it through much, but contenders are:

  • Files - ("Give me a listing of the current state of the working directory")
  • File finders - ("Give me access to the file x")
  • Content - ("Give me the content of Gemspec.lock at this revision")
  • Size-related - ("What's the size of this file")

You know, things that would help out in, say, every single Probe we ever write.

We also will need to abstract this out like we do Sources and Probes- define the common interface and then override those methods in each subclass. Subclasses:

  • Git (via Rugged::Repository)
  • Subversion (via Who::The::Fuck::Knows)
  • Disk (via stdlib, just a wrapper over a bare filesystem download if something's not in version control)

Disk could be tricky- since we wouldn't have any version control history, the whole concept of snapshots falls down. We might want a way to bypass snapshotting and only report one (the HEAD) number.

Swearing: commits

Look for swearing in commits, too.

Let's face it, this shit can be fuckin' frustrating.

Maybe swearing will be statistically significant for determining the popularity of a project, who knows.

Fix or rip out Flay

Like Flog, don't shell out to Flay. Seems like it may be possible (especially with the new Repository stuff). If it's not doable, that means we can't really run versioned Flay runs, so we should just rip it out.

Comment %

Compare number of comments versus LOC

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.