Skip to content
Snippets Groups Projects

Issue #3321492: Replace README.txt with README.md

Open Issue #3321492: Replace README.txt with README.md
issue/nomarkup-3321492:1.x into 1.x
4 unresolved threads
Open Asha Patel requested to merge issue/nomarkup-3321492:1.x into 1.x
4 unresolved threads

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
README.md 0 → 100644
18 - Information for developers
19 - Maintainers
20
21
22 ## Requirements
23
24 This module requires no modules outside of Drupal core.
25
26
27 ## Installation
28
29 Install as you would normally install a contributed Drupal module. For further
30 information, see
31 [Installing Drupal Modules](https://www.drupal.org/docs/extending-drupal/installing-drupal-modules).
32
33
  • NISHANT THAKUR
    NISHANT THAKUR @thakurnishant_06 started a thread on an old version of the diff
    • README.md 0 → 100644
    44
    45 Without this module one can use:
    46
    47 `headline: content.field_band_headline|render|striptags|trim,`
    48
    49 This is problematic due to the double rendering involved. So if the headline were `Foos&Bars` for example, it would render as `Foos&Bars`.
    50
    51 Another alternative is using the field data directly from Twig.
    52
    53 `headline: node.field_band_headline['#items'][0].value`
    54
    55 This can lead to security problems as the user input data is not properly sanitized by the input filters in the render pipeline.
    56
    57 ## Maintainers
    58
    59 Supporting by:
  • Nitin Lama added 1 commit

    added 1 commit

    • 8359fa64 - #3321492 Addressing comments in the MR4, and fixing white trailing issue and indentations.

    Compare with previous version

  • Alberto Paderno added 6 commits

    added 6 commits

    Compare with previous version

  • Alberto Paderno added 1 commit

    added 1 commit

    • 1379cf41 - Improved formatting; added content to an empty section

    Compare with previous version

  • Alberto Paderno added 1 commit

    added 1 commit

    • 98b86969 - Corrected the module name used in the README.md file; slightly improved the text formatting

    Compare with previous version

  • Alberto Paderno added 1 commit

    added 1 commit

    • c982334e - Added the missing periods at the end of two sentences

    Compare with previous version

  • Mateu Aguiló Bosch
    Mateu Aguiló Bosch @e0ipso started a thread on the diff
    • README.md 0 → 100644
    23 ## Requirements
    24
    25 This module requires no modules outside of Drupal core.
    26
    27
    28 ## Installation
    29
    30 Install as you would normally install a contributed Drupal module. For further
    31 information, see
    32 [Installing Drupal Modules](https://www.drupal.org/docs/extending-drupal/installing-drupal-modules).
    33
    34
    35 ## Configuration
    36
    37 The module does not have its own menus. The module implements a Views style
    38 plugin to display rows without any additional markup.
  • Mateu Aguiló Bosch
    Mateu Aguiló Bosch @e0ipso started a thread on the diff
    • README.md 0 → 100644
    30 Install as you would normally install a contributed Drupal module. For further
    31 information, see
    32 [Installing Drupal Modules](https://www.drupal.org/docs/extending-drupal/installing-drupal-modules).
    33
    34
    35 ## Configuration
    36
    37 The module does not have its own menus. The module implements a Views style
    38 plugin to display rows without any additional markup.
    39
    40 ## Usage
    41
    42 Use this module to remove all the cruft without weakening the site security.
    43 Edit the display mode and remove the field markup for field_band_headline and
    44 field_band_subheader. content.field_band_headline will now contain only the
    45 field value, without the wrapping markup.
    • Comment on lines +42 to +45
      Mateu Aguiló Bosch
      Mateu Aguiló Bosch @e0ipso
      Maintainer

      I think we should keep away from naming specific fields. Alternatively we can add code samples and then use the specific field names.

      Please take a look at the project page.

    • Please register or sign in to reply
    Please register or sign in to reply