Browse Source

docs: unify ../ <> ./../ (#7434)

Dariusz Rumiński 1 year ago
parent
commit
1b2cb2065a
3 changed files with 9 additions and 9 deletions
  1. 1 1
      doc/config.rst
  2. 4 4
      doc/cookbook_fixers.rst
  3. 4 4
      doc/custom_rules.rst

+ 1 - 1
doc/config.rst

@@ -13,7 +13,7 @@ It is possible to *not* have the config file. In that case, the default rule set
 
 It is also possible to provide command line options to customize rules, yet instead of using them,
 it's recommended to save the project configuration in a ``.php-cs-fixer.dist.php`` file in the root directory of your project.
-The file must return an instance of `PhpCsFixer\\ConfigInterface <../src/ConfigInterface.php>`_
+The file must return an instance of `PhpCsFixer\\ConfigInterface <./../src/ConfigInterface.php>`_
 which lets you configure the rules, the files and directories that
 need to be analyzed. You may also create ``.php-cs-fixer.php`` file, which is
 the local configuration that will be used instead of the project configuration. It

+ 4 - 4
doc/cookbook_fixers.rst

@@ -523,10 +523,10 @@ Why am I asked to use ``getPrevMeaningfulToken()`` instead of ``getPrevNonWhites
   or a whitespace, the returned token will always be ``->``.
 
 .. _Composer: https://getcomposer.org
-.. _CONTRIBUTING.md: ../CONTRIBUTING.md
+.. _CONTRIBUTING.md: ./../CONTRIBUTING.md
 .. _idempotent: https://en.wikipedia.org/wiki/Idempotence#Computer_science_meaning
 .. _Linus's Law: https://en.wikipedia.org/wiki/Linus%27s_Law
 .. _List of Parser Tokens: https://php.net/manual/en/tokens.php
-.. _Token class: ../src/Tokenizer/Token.php
-.. _Tokens class: ../src/Tokenizer/Tokens.php
-.. _Transformers: ../src/Tokenizer/Transformer
+.. _Token class: ./../src/Tokenizer/Token.php
+.. _Tokens class: ./../src/Tokenizer/Tokens.php
+.. _Transformers: ./../src/Tokenizer/Transformer

+ 4 - 4
doc/custom_rules.rst

@@ -6,7 +6,7 @@ If you need to enforce some specific code style rules, you can implement your
 own fixers.
 
 For each rule you want to add, create a class that implements
-`PhpCsFixer\\Fixer\\FixerInterface <../src/Fixer/FixerInterface.php>`_.
+`PhpCsFixer\\Fixer\\FixerInterface <./../src/Fixer/FixerInterface.php>`_.
 Note that there is a specific constraint
 regarding custom rules names: they must match the pattern
 ``/^[A-Z][a-zA-Z0-9]*\/[a-z][a-z0-9_]*$/``.
@@ -32,6 +32,6 @@ Then register your custom fixers and enable them in the config file:
 
 There are several interfaces that your fixers can also implement if needed:
 
-* `PhpCsFixer\\Fixer\\WhitespacesAwareFixerInterface <../src/Fixer/WhitespacesAwareFixerInterface.php>`_: for fixers that need to know the configured indentation and line endings;
-* `PhpCsFixer\\Fixer\\ConfigurableFixerInterface <../src/Fixer/ConfigurableFixerInterface.php>`_: to create a configurable fixer;
-* `PhpCsFixer\\Fixer\\DeprecatedFixerInterface <../src/Fixer/DeprecatedFixerInterface.php>`_: to deprecate a fixer.
+* `PhpCsFixer\\Fixer\\WhitespacesAwareFixerInterface <./../src/Fixer/WhitespacesAwareFixerInterface.php>`_: for fixers that need to know the configured indentation and line endings;
+* `PhpCsFixer\\Fixer\\ConfigurableFixerInterface <./../src/Fixer/ConfigurableFixerInterface.php>`_: to create a configurable fixer;
+* `PhpCsFixer\\Fixer\\DeprecatedFixerInterface <./../src/Fixer/DeprecatedFixerInterface.php>`_: to deprecate a fixer.