Replies: 1 comment 2 replies
-
These are some of the features I have written around the current system:
Not sure how these would all translate to using a new Pipeline model, but happy to provide code samples if required. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@StefanBertels has mentioned using a pipeline to process records. I came across this when converting the docs site over to Statiq as it's heavily used there. It makes modifying the behavior of the system really simple.
virtual
methods/members with someprotected
isn't cutting it since moving config and state internal to the classes. Making more thingsprotected
just causes a lot or problems.A pipeline would allow any part of the system to easily be changed, added, or removed. It would also give a lot more visibility into how the system behaves.
What are some features that people would like to see in the system? I'd like to make sure what is built can handle them.
I'll start a list and add things as they come in.
Func
s ordelegate
s to allow simple lambda expressions as a step. This should allow a user to create their own re-usable library to plug in.Beta Was this translation helpful? Give feedback.
All reactions