This document is a short how-to. It doesn't contain a lot of details about each change you need to implement, but it contains lots of links to the corresponding documents. Please read these docs for refetence.
ESLint is the main tool to find deprecations in the code so first of all we need to configure it properly.
Dear XCorp / Hi, XCorp depending on familiarity
I'm writing in response to X, where you advertised a vacancy for Y. I am interested in applying for this role -- please find my CV attached.
My current employment position is X, which means I'm responsible for delivering/organising/producing A, B, and C. I was previously the Y at Z where I did D. My main responsibility / largest project here has been P, which is a Widget that produces Doo-dads.
While I enjoy working at X for reasons K and L, I find M frustrating. I'm also looking to move on into areas such as N, P and Q, without losing touch with K. I find K valuable but I would prefer to change my working environment to include P.
I'm particularly interested in XCorp because, as well as providing the career experience I'm after, I use your product / admire your work / look up to your staff for these reasons: ...
The -j option of the application generator accepts an arbitrary string. If passed "foo", the gem "foo-rails" is added to the Gemfile, and the application JavaScript manifest requires "foo" and "foo_ujs". As of this writing "prototype-rails" and "jquery-rails" exist and provide those files via the asset pipeline. Default is "jquery". [fxn]
jQuery is no longer vendored, it is provided from now on by the jquery-rails gem. [fxn]
Prototype and Scriptaculous are no longer vendored, they are provided from now on by the prototype-rails gem. [fxn]
The scaffold controller will now produce SCSS file if Sass is available [Prem Sichanugrist]
