Permalink
Commits on Oct 11, 2010
  1. data-disable-with in button_to helper

    Paco Guzman authored and spastorino committed Oct 11, 2010
    [#4993 state:committed]
    
    Signed-off-by: Santiago Pastorino <santiago@wyeworks.com>
  2. Revert "Add missing CHANGELOG entry about reset_javascript_include_de…

    fxn committed Oct 11, 2010
    …fault"
    
    This reverts commit 234a4ca.
    
    Reason: No big deal Ryan, only there's a very strict policy in
    docrails which allows public write access on the other hand.
    CHANGELOGs can only be edited in master. If this is added I'll
    make sure you get the credit for the patch.
  3. Updated DOCS for engines and added a couple TODOs. Also, commented in…

    josevalim committed Oct 11, 2010
    …ternal railties rake tasks description.
  4. I corrected a code snippet typo in the railties/guides/source/initial…

    fooledbyprimes authored and radar committed Oct 11, 2010
    …ization.textile file [#5779 state:resolved]
  5. Updated RUNNING_UNIT_TESTS documentation with mention of the build_da…

    NathanZook authored and radar committed Oct 11, 2010
    …tabases rake tasks.
Commits on Oct 10, 2010
  1. Revert "Make InstanceTagMethods#value_before_type_cast raise if the m…

    spastorino committed Oct 10, 2010
    …odel don't respond to attr_before_type_cast or attr method"
    
    And    "Makes form_helper use overriden model accessors"
    
    This reverts commit 3ba8e31 and fb0bd8c.
  2. Make ActiveSupport load own version.

    bsears authored and spastorino committed Sep 29, 2010
    [#5739 state:committed]
    
    Signed-off-by: Santiago Pastorino <santiago@wyeworks.com>
  3. Fix misleading advice to add 'memcache' to Gemfile

    wincent authored and spastorino committed Sep 2, 2010
    [#5539 state:committed]
    
    Commit 5714438 removed the hard-coded dependency on the memcache-client
    gem, and added this warning advising people to install it if needed. The
    problem is, however, that if people follow the advice literally and install
    the 'memcache' gem, they will wind up with a completely different thing,
    which is not API compatible with the memcache-client gem and which Rails
    can't work with.
    
    So, be explicit and tell users to install the 'memcache-client' gem.
    
    Signed-off-by: Santiago Pastorino <santiago@wyeworks.com>
  4. Override #store to be consistent with #[].

    andreacampi authored and spastorino committed Oct 9, 2010
    [#5775 state:resolved]
    
    Signed-off-by: Santiago Pastorino <santiago@wyeworks.com>
  5. Update CHANGELOG.

    josevalim committed Oct 10, 2010
  6. Add support to render :once.

    josevalim committed Oct 10, 2010
    This will be used internally by sprockets to ensure requires are executed just once.
  7. Clean up the house before moving in the new furniture.

    josevalim committed Oct 10, 2010
    This commit moves all the template rendering logic that was hanging around AV::Base to renderer objects.
  8. prevent rake test to run the test suite three times when ENV['TEST'] …

    calavera authored and fxn committed Oct 8, 2010
    …is set [#3572 state:resolved]
    
    Signed-off-by: Xavier Noria <fxn@hashref.com>
  9. Resolvers now consider timestamps.

    josevalim committed Oct 10, 2010
    Before this patch, every request in development caused the template
    to be compiled, regardless if it was updated in the filesystem or not.
    This patch now checks the timestamp and only compiles it again if
    any change was done.
    
    While this probably won't show any difference for current setups,
    but it will be useful for asset template handlers (like SASS), as
    compiling their templates is slower than ERb, Haml, etc.
Commits on Oct 9, 2010
  1. Rename rake railties:copy_migrations to rake railties:install:migrati…

    drogus committed Oct 9, 2010
    …ons and fix it to work with new copying strategy
  2. Change the method for copying migrations, do not add scope.

    drogus committed Oct 8, 2010
    The purpose of this change is to allow copying fail on the same names.
    Migrations change database and they should be treated with caution,
    if 2 migrations are named the same it's much better to skip migration
    and allow user decide if it should be copied or not.