Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on May 4, 2015
  1. @pixeltrix

    Improve display of attachment names in mailer previews

    pixeltrix authored
    Display attachment filenames as a comma separated list rather than
    showing the inspect output for the array.
  2. @pixeltrix

    Fix mailer previews with attachments

    pixeltrix authored
    Use the mail gem's own API to locate the correct part.
    
    Fixes #14435.
Commits on Apr 30, 2015
  1. @remomueller

    Mailer preview now uses `url_for` to fix links to emails for apps run…

    remomueller authored
    …ning on a subdirectory, closes #19092.
Commits on Apr 28, 2015
  1. @senny
  2. @senny

    mailer previews, make sure labels and values line up.

    senny authored
    While this was true before when every `dd` had a value,
    this patch makes sure that everything keeps lining up even
    when the `dd` node is blank.
Commits on Apr 23, 2015
  1. @cllns
Commits on Nov 27, 2014
  1. @fxn

    rails -> bin/rails in index.html

    fxn authored
Commits on Oct 29, 2014
  1. @edwinwills

    On larger screens the email preview iframe is being limited to a heig…

    edwinwills authored
    …ht of 800 pixels, and the full available screen size is not being used.
Commits on Sep 25, 2014
  1. @bronzle

    remove extra # in css

    bronzle authored
  2. @rafaelfranca

    :nail_care: the CSS

    rafaelfranca authored
  3. @buddhamagnet
Commits on Sep 9, 2014
  1. @slavingia
Commits on Dec 17, 2013
  1. @dhh

    Remove the navigator for now. Its ugly and it promises more than it c…

    dhh authored
    …an deliver. These other views (properties, routes) are not designed to be loaded in isolation
  2. @pixeltrix
Commits on Nov 22, 2013
  1. @sbagdat

    Fix for titles of info pages

    sbagdat authored
    Both `rails/info/properties` and `rails/info/routes` have same html
    title attribute as *Routes*. This commit includes a fix for the titles.
Commits on Jul 22, 2013
  1. @drogus

    Revert "Match Dev/Prod parity for Index Page"

    drogus authored
    Showing welcome page in production can expose information, which should
    not be visible on production if people don't override the default root
    route.
    
    This reverts commit b0caea2.
  2. @drogus

    Merge pull request #11514 from schneems/schneems/dev-prod-parity-index

    drogus authored
    Match Dev/Prod parity for Index Page
Commits on Jul 20, 2013
  1. @schneems

    Match Dev/Prod parity for Index Page

    schneems authored
    With Rails 4 the default index page was moved from a static file `index.html` inside the `public/` folder to an internal controller/view inside of the railties gem. This was to allow use of erb in the default index page and to remove the requirement that new apps must delete a static file to make their index pages work. While this was a good change, the functionality was unexpected to developers who wish to get their apps running in production ASAP. They will create a new app `rails new my app`, start a server to verify it works, then immediately deploy the app to verify that it can start working in production. Unfortunately locally they see a page when they visit `localhost:3000` when they visit their production app they get an error page.
    
    We initially anticipated this problem in the original pull request, but did not properly anticipate the severity or quantity of people who would like this functionality. Having a default index page serves as an excellent litmus test for a passed deploy on default apps, and it is very unexpected to have a page work locally, but not on production. 
    
    This change makes the default index page available in production if the developer has not over-written it by defining their own `root` path inside of routes.
  2. @prathamesh-sonpatki

    Removed information about creating database[ci skip]

    prathamesh-sonpatki authored
    - As default index page is no longer in public folder, rails hits the
      welcome controller in railties for index action
    - If the database is not created or username and password are
      incorrect in database.yml, those errors are first shown before index
      action succeeds
    - welcome#index succeeds iff the database is created with correct
      details in database.yml
    - So this information about creating database is not required in the
      index template
Commits on Apr 2, 2013
  1. @steveklabnik

    Remove rails.png.

    steveklabnik authored
    No reason to have a file, we've got data-URIs now! It didn't make sense
    to me that you no longer have to remove public/index.html, but you still
    need to remove rails.png. This means that you won't have to any more
    when making a new Rails app.
Commits on Jan 8, 2013
  1. @tricknotes

    Use absolute path

    tricknotes authored
    It is semantically correct than relative path.
Commits on Jan 6, 2013
  1. @carlosantoniodasilva

    Move table routes formatter class to the inspector and rename it

    carlosantoniodasilva authored
    It feels more consistent to have this class called "HtmlTableFormatter",
    and to have it here with the routes inspector and console formatter,
    since it's used for both routing error exceptions and the rails info
    page.
  2. @carlosantoniodasilva
Commits on Jan 5, 2013
  1. @goshakkk
  2. @carlosantoniodasilva
  3. @carlosantoniodasilva
  4. @tricknotes
Commits on Jan 4, 2013
  1. @franckverrot
  2. @tricknotes
Commits on Jan 1, 2013
  1. @vijaydev
Commits on Dec 17, 2012
  1. @schneems

    Format routes as html on debug page

    schneems authored
    When someone gets a routing exception, the routes are rendered (starting in Rails 4.0). This PR brings parity between the html routes in the `rails/info/routes` path and when rendered from an exception. This is the continuation of #8521 which brought html formatted routes. 
    
    In addition to bringing parity to the two views, we're keeping our views DRY by rendering off of the same partials. In this case Railties depends on partials provided by ActionDispatch. I'm open to alternative implementations. Ideally both views will use the same code so any improvements or updates to it will be reproduced on both.
    
    <hr />
    
    ![](http://f.cl.ly/items/3O1D0K1v0j0i343O3T3T/Screen%20Shot%202012-12-17%20at%203.07.20%20PM.png)
  2. @schneems

    HTML formatting to Rails::InfoController#routes

    schneems authored
    This PR adds formatting and meta-data to the display of the internal routes. Users can now toggle between showing helpers with the `_path` or _`url` suffix. 
    
    There are multiple ways to achieve this, this method uses partials for formatting and meta-data. The partials can be re-used when rendering `routing_error.erb`, though that will need to be in a separate PR.
    
    ![](http://f.cl.ly/items/3A2p3c1T1t2f2X2R2K2S/Screen%20Shot%202012-12-12%20at%202.28.01%20PM.png)
    
    
    ATP Railties
Commits on Dec 14, 2012
  1. @steveklabnik

    Revert "Merge pull request #8499 from schneems/schneems/html-route-in…

    steveklabnik authored
    …spector"
    
    This reverts commit ae68fc3, reversing
    changes made to 0262a18.
    
    See here: #8499 (comment)
Commits on Dec 12, 2012
  1. @schneems

    Output routes in :html format

    schneems authored
    By formatting routes for different media (txt/html) we can apply optimizations based on the format. We can include meta-data in the HTML to allow a rich experience while rendering and viewing the routes. This PR shows route helpers as they are used with the `_path` extension, it also has a javascript toggle on the top to switch to `_url`. This way the developer can see the exact named route helper they can use instead of having to modify a base. 
    
    This is one example of an optimization that could be applied. Eventually we can link out to guides for the different columns to better explain what helper, HTTP Verb, Path, and Controller#action indicate. We could even add a route search box that could allow developers to input a given route and see all of the routes that match it. These are stand alone features and should be delivered separately.
Commits on Dec 11, 2012
  1. @georgeclaghorn

    Explain how to supersede the new dynamic welcome page

    georgeclaghorn authored
    The old, static welcome page instructed developers to delete the
    public/index.html file and set a root route.  The new, dynamic welcome
    page should tell developers (a) why they're seeing it when it doesn't
    correspond to anything in the viewable app source and (b) that it can
    be superseded with a root route.
Something went wrong with that request. Please try again.