Skip to content

Commit

Permalink
Fix wording and examples
Browse files Browse the repository at this point in the history
  • Loading branch information
mostafa committed Jun 29, 2023
1 parent c87286c commit 575ff70
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ class Pipeline_2(Pipeline):
)
```

Both pipelines can still be used in the same manner as before. There is no difference between the two approaches because the `Pipeline_2` class can be instantiated and used as a pipeline object. In other words, when the class is instantiated, the `apply` method is automatically called, which returns a `ProcessingPipeline` object. This behavior aligns with the functionality of the `pipeline_1` function, which also returns a `ProcessingPipeline` object. This consistency results in a cleaner and more streamlined approach for autodiscovery and facilitates the gradual migration of pipeline functions to classes.
Both pipelines can still be used in the same manner as before. There is no difference between the two approaches because the `Pipeline_2` class can be instantiated and used as a pipeline object, like `Pipeline_2()()` or `Pipeline_2().apply()`. In other words, when the class is instantiated, an object of the `Pipeline` class is returned. Calling the object itself will automatically run the `apply` method, which returns a `ProcessingPipeline` object. This behavior aligns with the functionality of the `pipeline_1` function, which also returns a `ProcessingPipeline` object. This consistency results in a cleaner and more streamlined approach for autodiscovery and facilitates the gradual migration of pipeline functions to classes.

### pySigma before v0.9.11

Expand Down

0 comments on commit 575ff70

Please sign in to comment.