[1.x] Flex Processor

Created on 4 October 2024, about 2 months ago

Flex processor overview

Flex Process is a versatile Drupal module designed to empower developers with the ability to attach customizable processor plugins to various data structures. This tool allows developers to define specific processing workflows for their data, enabling dynamic manipulation and transformation.

How it works

This module provides the ability to create data processor plugins in a simple way. Every time a data, form now on data component, is sent to be processed, the corresponding plugin matching that data component type is executed. The processors plugin are defined in a flexible way that any kind of processing task is allowed. How to process to process the data component is up to the developer, and they needs.

Project Link

https://www.drupal.org/project/flex_processor →

📌 Task
Status

Needs review

Component

module

Created by

🇦🇷Argentina ivan.lansky

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @ivan.lansky
  • 🇮🇳India vishal.kadam Mumbai

    Thank you for applying!

    Please read Review process for security advisory coverage: What to expect → for more details and Security advisory coverage application checklist → to understand what reviewers look for. Tips for ensuring a smooth review → gives some hints for a smoother review.

    The important notes are the following.

    • If you have not done it yet, you should run phpcs --standard=Drupal,DrupalPractice on the project, which alone fixes most of what reviewers would report.
    • For the time this application is open, only your commits are allowed.
    • The purpose of this application is giving you a new drupal.org role that allows you to opt projects into security advisory coverage, either projects you already created, or projects you will create. The project status won't be changed by this application and no other user will be able to opt projects into security advisory policy.
    • We only accept an application per user. If you change your mind about the project to use for this application, or it is necessary to use a different project for the application, please update the issue summary with the link to the correct project and the issue title with the project name and the branch to review.

    To the reviewers

    Please read How to review security advisory coverage applications → , Application workflow → , What to cover in an application review → , and Tools to use for reviews → .

    The important notes are the following.

    • It is preferable to wait for a Code Review Administrator before commenting on newly created applications. Code Review Administrators will do some preliminary checks that are necessary before any change on the project files is suggested.
    • Reviewers should show the output of a CLI tool → only once per application.
    • It may be best to have the applicant fix things before further review.

    For new reviewers, I would also suggest to first read In which way the issue queue for coverage applications is different from other project queues → .

  • 🇮🇳India vishal.kadam Mumbai

    Fix phpcs issues.

    phpcs --standard=Drupal,DrupalPractice --extensions=php,module,inc,install,test,profile,theme,css,info,txt,md,yml flex_processor/
    
    FILE: flex_processor/flex_processor.services.yml
    ----------------------------------------------------------------------------
    FOUND 1 ERROR AFFECTING 1 LINE
    ----------------------------------------------------------------------------
     6 | ERROR | [x] Expected 1 newline at end of file; 0 found
    ----------------------------------------------------------------------------
    PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
    ----------------------------------------------------------------------------
    
    FILE: flex_processor/README.md
    ----------------------------------------------------------------------------
    FOUND 28 ERRORS AND 6 WARNINGS AFFECTING 28 LINES
    ----------------------------------------------------------------------------
       3 | WARNING | [ ] Line exceeds 80 characters; contains 292 characters
       8 | WARNING | [ ] Line exceeds 80 characters; contains 407 characters
      12 | WARNING | [ ] Line exceeds 80 characters; contains 145 characters
      16 | WARNING | [ ] Line exceeds 80 characters; contains 90 characters
      54 | WARNING | [x] A comma should follow the last multiline array item. Found: ]
      56 | ERROR   | [x] Expected 1 blank line after function; 0 found
      57 | ERROR   | [x] The closing brace for the class must have an empty line before it
      64 | ERROR   | [x] Line indented incorrectly; expected 0 spaces, found 2
      65 | ERROR   | [x] Line indented incorrectly; expected 0 spaces, found 2
      70 | ERROR   | [x] Line indented incorrectly; expected 0 spaces, found 4
      74 | ERROR   | [x] Line indented incorrectly; expected 0 spaces, found 6
      77 | ERROR   | [x] Line indented incorrectly; expected 0 spaces, found 2
      87 | ERROR   | [x] Expected 1 space after "<"; 0 found
      87 | ERROR   | [x] Expected 1 space before "?"; 0 found
      87 | ERROR   | [x] Expected 1 space after "?"; 0 found
     129 | ERROR   | [x] Use statements should be sorted alphabetically. The first wrong one is Drupal\flex_processor\Component\DataComponent.
     131 | ERROR   | [x] Line indented incorrectly; expected 0 spaces, found 2
     132 | ERROR   | [ ] The array declaration extends to column 93 (the limit is 80). The array content should be split up over multiple lines
     135 | ERROR   | [x] Line indented incorrectly; expected 0 spaces, found 2
     137 | ERROR   | [x] Line indented incorrectly; expected 0 spaces, found 2
     142 | ERROR   | [x] Line indented incorrectly; expected 0 spaces, found 4
     160 | WARNING | [x] A comma should follow the last multiline array item. Found: }
     176 | ERROR   | [x] Expected 1 space after "<"; 0 found
     176 | ERROR   | [x] Expected 1 space before "?"; 0 found
     176 | ERROR   | [x] Expected 1 space after "?"; 0 found
     183 | ERROR   | [x] Missing class doc comment
     207 | ERROR   | [x] Functions must not contain multiple empty lines in a row; found 2 empty lines
     228 | ERROR   | [x] Expected 1 space after "<"; 0 found
     228 | ERROR   | [x] Expected 1 space before "?"; 0 found
     228 | ERROR   | [x] Expected 1 space after "?"; 0 found
     266 | ERROR   | [x] Line indented incorrectly; expected 0 spaces, found 2
     268 | ERROR   | [x] Line indented incorrectly; expected 0 spaces, found 2
     273 | ERROR   | [x] Line indented incorrectly; expected 0 spaces, found 4
     276 | ERROR   | [x] Expected 1 newline at end of file; 0 found
    ----------------------------------------------------------------------------
    PHPCBF CAN FIX THE 29 MARKED SNIFF VIOLATIONS AUTOMATICALLY
    ----------------------------------------------------------------------------
    
    FILE: flex_processor/flex_processor.info.yml
    ----------------------------------------------------------------------------
    FOUND 1 ERROR AFFECTING 1 LINE
    ----------------------------------------------------------------------------
     7 | ERROR | [x] Expected 1 newline at end of file; 0 found
    ----------------------------------------------------------------------------
    PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
    ----------------------------------------------------------------------------
    
  • 🇦🇷Argentina ivan.lansky

    Hi!
    Thanks for your time to make the review.

    Is it common to analyze MD files with PHPCS? I had to add some exceptions to make it work properly.

  • 🇮🇳India vishal.kadam Mumbai

    Yes, It is common to analyze MD files with PHPCS.

    Rest seems fine to me. Let’s wait for other reviewers to take a look and if everything goes fine, you will get the role.

  • 🇦🇷Argentina ivan.lansky

    I am changing priority as per Issue priorities → .

Production build 0.71.5 2024