Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: voxpupuli/json-schema
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 0.1.10
Choose a base ref
...
head repository: voxpupuli/json-schema
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 0.1.14
Choose a head ref
  • 15 commits
  • 35 files changed
  • 1 contributor

Commits on Feb 15, 2011

  1. Added schema to error output messages and added ability to self-refer… 

    …ence schemas (thanks, @Vasfed)
    @hoxworth
    hoxworth committed Feb 15, 2011
    Configuration menu
    Copy the full SHA
    361e8ef View commit details
    Browse the repository at this point in the history

Commits on Feb 16, 2011

  1. Added gemspec

    @hoxworth
    hoxworth committed Feb 16, 2011
    Configuration menu
    Copy the full SHA
    032f672 View commit details
    Browse the repository at this point in the history

  2. And this actually adds the gemspec, heh

    @hoxworth
    hoxworth committed Feb 16, 2011
    Configuration menu
    Copy the full SHA
    7495466 View commit details
    Browse the repository at this point in the history

  3. Adding format rules

    @hoxworth
    hoxworth committed Feb 16, 2011
    Configuration menu
    Copy the full SHA
    36735a5 View commit details
    Browse the repository at this point in the history

  4. Updating README

    @hoxworth
    hoxworth committed Feb 16, 2011
    Configuration menu
    Copy the full SHA
    b3b0a66 View commit details
    Browse the repository at this point in the history

Commits on Feb 17, 2011

  1. Factoring out all of the attribute validations into classes and intro… 

    …ducing the concept of individual validators. Will work on getting draft 2 working next.
    @hoxworth
    hoxworth committed Feb 17, 2011
    Configuration menu
    Copy the full SHA
    29b7658 View commit details
    Browse the repository at this point in the history

Commits on Feb 18, 2011

  1. Ignore those generated gems sitting around in my top-level directory.

    @hoxworth
    hoxworth committed Feb 18, 2011
    Configuration menu
    Copy the full SHA
    6be82f8 View commit details
    Browse the repository at this point in the history

  2. Clean up the method calls. Add 'validate!' and alias it to 'validate2… 

    …' for backwards compatibility.
    @hoxworth
    hoxworth committed Feb 18, 2011
    Configuration menu
    Copy the full SHA
    3c411d0 View commit details
    Browse the repository at this point in the history

  3. Fix the validate methods and convert the tests over to be draft3 spec… 

    …ific.
    @hoxworth
    hoxworth committed Feb 18, 2011
    Configuration menu
    Copy the full SHA
    e966c06 View commit details
    Browse the repository at this point in the history

Commits on Mar 9, 2011

  1. It makes far more sense to go through each attribute in the schema an… 

    …d see if the current validator supports it as opposed to going through each supported validator attribute and seeing if the current schema includes it.
    @hoxworth
    hoxworth committed Mar 9, 2011
    Configuration menu
    Copy the full SHA
    b0c10f0 View commit details
    Browse the repository at this point in the history

  2. I apparenntly included the extended schema stuff with the last commit… 

    …. Well, here is the start of testing for that.
    @hoxworth
    hoxworth committed Mar 9, 2011
    Configuration menu
    Copy the full SHA
    997504e View commit details
    Browse the repository at this point in the history

  3. Change the name of this test.

    @hoxworth
    hoxworth committed Mar 9, 2011
    Configuration menu
    Copy the full SHA
    bf7ca92 View commit details
    Browse the repository at this point in the history

  4. Update version and update the README to be a bit more useful

    @hoxworth
    hoxworth committed Mar 9, 2011
    Configuration menu
    Copy the full SHA
    f2daf85 View commit details
    Browse the repository at this point in the history

  5. How did that code get out of my <pre>?

    @hoxworth
    hoxworth committed Mar 9, 2011
    Configuration menu
    Copy the full SHA
    646654a View commit details
    Browse the repository at this point in the history

  6. One more README update to better reflect the version we are now suppo… 

    …rting.
    @hoxworth
    hoxworth committed Mar 9, 2011
    Configuration menu
    Copy the full SHA
    f27759a View commit details
    Browse the repository at this point in the history
Loading