New to Rails but looks like everything for an engine should be done inside the engine's folder. The updated text has been there for a long time so I hope I'm not just missing something. At this point in the example the user does not have an application (that comes in the next section) and elsewhere in the doc there is talk of the importance of running the commands from the *engine* root so it seems more consistent to talk about "engine root" as updated.

The Terminology section of the Action Cable guide currently is one large
text without any headings. Instead of having one large text, we can use
headings to describe all terminology for easier scanability and improved
table of contents.

The Broadcastings section mentions Pub/Sub so it's moved beneath the Pub/Sub
section.

The following part is moved up to the Connections terminology section.
It makes more sense to have it where it introduces the term.
> Connections form the foundation of the client-server relationship.

Update guides/source/testing.md
Co-authored-by: NJonathan Hefner <jonathan@hefner.pro>

Update guides/source/plugins.md
Co-authored-by: NJonathan Hefner <jonathan@hefner.pro>

Fixes the spelling of DigitalOcean in the ActiveStorage guide.

parent f4471fc7
author Sandip Mane <sandip.mane@bigbinary.com> 1593247595 +0530
committer Sandip Mane <sandip2490@gmail.com> 1597253412 +0530

Adds doc for habtm association for always optional: true

Added docs line under definition of habtm with a text containing habtm refers to zero or more associations

Added docs line under definition of habtm with a text containing it refers to zero or more associations

Updated the sentence to include declaring association for habtm relation

Update security.md to note that CSRF security token is included in requests automatically when `config.action_controller.default_protect_from_forgery` is set to `true`, which is the default for newly created Rails applications.

The GitHub gist API page is out of date. This commit replaces it with
the new link.

Also, removed unnecessary commas, added missing fullstop and fixed
a ruby snippet which wasn't rendered correctly before.

These formats were added in c329d323 and
bcf370d6, respectively.

Mentioning the baseline default for a config option can be confusing
when that default is overridden by `config.load_defaults`.  To avoid
that confusion, this commit relocates such baseline defaults from their
explanatory paragraphs to a "Baseline defaults" section that flows with
the other `config.load_defaults` sections.

Ideally, when we override other baseline defaults in the future, we will
relocate mention of them as done here.

Closes #39387.

Adds documentation for https://github.com/rails/rails/pull/39866

Followup to 17a4ec1c.

When using Rouge's Console lexer it expects all ignored line breaks to
be proceeded by a backslash. In this code block as we are switching to
Mysql's command line which doesn't need a backslash. This leads to the
lexer breaking and all the lines ending up in a confusing mess.

However the sql syntax actually works much better for this block
anyway.

This line here shows why what we were trying to do wouldn't work with
Rouge:
https://github.com/rouge-ruby/rouge/blob/844c0eeddf7626605fa04b901df6c15c953811d6/lib/rouge/lexers/console.rb#L106

We recently switched to use Rouge for syntax highlighting in the guides,
but in doing so we dropped support for highlighting the following
syntaxes, which are used in the guides:

apache
diff
json
markdown
nginx
scss
xml

There was also css and the "javascript" alias, but @eugeneius already
addressed these two.

They syntaxes were all being converted to "plaintext". This change allows
all the lexers mentioned above as well as any other lexers available
through Rouge.

We have deliberately decided to not support passing rougue custom lexer
options from the code fences. Instead any lexer options that are needed
can be set by adding an entry to the lexer_language case statement. This
should lead to more consistency in formatting and gives us more control
over what Rogue options are allowed.

The `:include_blank` option of various `<select>`-related helpers causes
an `<option>` element with no content to be rendered.  However, the
[HTML spec] says that unless an `<option>` element has a `label`
attribute (which must be non-empty), its content must be "Text that is
not inter-element whitespace."

In #24923, this issue was addressed for `select_tag` by adding a `label`
attribute to the `<option>`.  This commit addresses the issue in the
same manner for `FormBuilder#select` and various date / time select
helpers.

[HTML spec]: https://html.spec.whatwg.org/multipage/form-elements.html#the-option-element

References #39367.

Also fix the language identifier for one JavaScript example.

In the getting started guide intro section both `-v` and `--version` are used:

    $ ruby -v
    $ sqlite3 --version
    $ node --version
    $ yarn -v
    $ rails --version

Both ruby and yarn support `--version` as well, but sqlite3 does not
support `-v`.

For consistency use `--version` option for `ruby` and `yarn` commands.

Follow-up to #39620.

This commit changes a few overlooked code fences to `bash`, and changes
a few IRB session snippets to be only Ruby code with a `ruby` fence.