aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/plugins.md
Commit message (Collapse)AuthorAgeFilesLines
* rails -> Rails [ci skip]Santosh Wadghule2016-07-121-1/+1
|
* use bin/rails default instead of rake commands [ci skip]Gaurav Sharma2016-01-191-1/+1
| | | I go through the `http://edgeguides.rubyonrails.org/` and found `rake` commands in various files that are in RAILS 5.0 implement by `bin/rails` command. I try to change all that can be directly use `bin/rails …`
* use `bin/test` in plugins guide [ci skip]yuuji.yaginuma2015-12-221-32/+67
| | | | | `bin/test` can use the same API as the `bin/rails test`, since it is possible to run a flexible test than rake, I think better to use a guide even `bin/test`.
* Introduce ApplicationRecord, an Active Record layer supertypeGenadi Samokovarov2015-12-161-10/+25
| | | | | | | | | | | | | | | | It's pretty common for folks to monkey patch `ActiveRecord::Base` to work around an issue or introduce extra functionality. Instead of shoving even more stuff in `ActiveRecord::Base`, `ApplicationRecord` can hold all those custom work the apps may need. Now, we don't wanna encourage all of the application models to inherit from `ActiveRecord::Base`, but we can encourage all the models that do, to inherit from `ApplicationRecord`. Newly generated applications have `app/models/application_record.rb` present by default. The model generators are smart enough to recognize that newly generated models have to inherit from `ApplicationRecord`, but only if it's present.
* [ci skip] fix inconsistent indentationJesse Doyle2015-11-171-1/+1
|
* remove link to outdated article in plugins guide [ci skip]yuuji.yaginuma2015-08-281-1/+0
| | | | linked article is a description of the plugins in Rails 2.1.
* use public Module#include instead of send :include [ci skip]yuuji.yaginuma2015-03-091-3/+3
|
* - Changed `IN` to `ON` in markdown renderer conditionVipul A M2015-01-141-1/+1
| | | | - Changed `IN` to `ON` in all note sentences in guides.
* warn about reading guides in GitHubXavier Noria2014-12-231-0/+2
| | | | References #18148.
* `bin/rake` does not exist in plugin directory [ci skip]yuuji.yaginuma2014-12-221-1/+1
|
* technical correction in guides under 'Generating an engine'David Elliott2014-09-281-2/+2
| | | | `bin/rails` would not exist outside of a rails project
* [ci skip] Update plugin doc with the latest railsYukio Mizuta2014-08-181-21/+21
|
* [ci skip] Fix broken url in plugins guideyuuji.yaginuma2014-08-121-1/+1
|
* Fix typo in plugins docGuillermo Álvarez Fernández2014-08-081-1/+1
|
* Use generated binstubs in guides examples.Josef Šimánek2014-05-201-7/+7
| | | | [ci skip]
* [skip ci] Standardized punctuation.ch33hau2014-02-251-3/+3
|
* Automatically maintain test database schemaJon Leighton2014-01-021-1/+0
| | | | | | | | | | | | | | * Move check from generated helper to test_help.rb, so that all applications can benefit * Rather than just raising when the test schema has pending migrations, try to load in the schema and only raise if there are pending migrations afterwards * Opt out of the check by setting config.active_record.maintain_test_schema = false * Deprecate db:test:* tasks. The test helper is now fully responsible for maintaining the test schema, so we don't need rake tasks for this. This is also a speed improvement since we're no longer reloading the test database on every call to "rake test".
* Formatting, capitalization, and punctuation fixes [ci skip]Ben Lewis2013-12-041-13/+17
| | | Second try on this commit.
* Call `rails plugin new yaffle` in the plugins guide. [ci skip]Ulysse Carion2013-10-081-3/+9
| | | | It's confusing to not explicitly do this step.
* [ci skip] Update plugins.mdHarshad Sabne2013-09-141-6/+6
| | | Highlighted code.
* cleans the guides sources from fancy non-ASCII stuffXavier Noria2013-08-231-1/+1
|
* fixes the test case of that pluginsRajarshi Das2013-07-181-4/+4
|
* Fix typo in rails plugins guideManish Valechha2013-01-271-1/+1
|
* Remove references to Rails versions.Steve Klabnik2012-12-071-4/+1
| | | | | | | | There's no reason for guides to reference old behaviors. They should be current as of the versions of Rails that they ship with, and including older information just clutters thing. I discussed this change with @fxn and he agrees.
* Fixed grammar in a lot of guide prologues.Katie Oldaker2012-12-071-2/+2
|
* Normalize on 'After reading this guide, you will know:'Steve Klabnik2012-11-291-1/+1
| | | | | We have three or four different introduction sentences to the guides. After this commit, we use the same one everywhere.
* Add periods to the bullet points in guides.Steve Klabnik2012-11-291-4/+4
| | | | Talked with @fxn about this. Bullet points should have periods at the ends.
* Switch to 1.9 hash syntax (guides)Agis Anastasopoulos2012-11-161-2/+2
|
* Fix remaining formatting problems in the guidePrem Sichanugrist2012-09-171-35/+35
|
* Convert all the links into Markdown formatPrem Sichanugrist2012-09-171-8/+8
|
* Convert all inline codes to Markdown syntaxPrem Sichanugrist2012-09-171-14/+14
|
* change shell to bashPrem Sichanugrist2012-09-171-12/+12
|
* Convert inline code tags to MarkdownPrem Sichanugrist2012-09-171-1/+1
|
* Convert heading tags and heading sectionPrem Sichanugrist2012-09-171-13/+21
|
* Convert code blocks into GFM stylePrem Sichanugrist2012-09-171-50/+50
|
* Rename the rest of the guides to MarkdownPrem Sichanugrist2012-09-171-0/+430