Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design high-level architecture #13

Open
joshua-light opened this issue Jan 9, 2023 · 1 comment
Open

Design high-level architecture #13

joshua-light opened this issue Jan 9, 2023 · 1 comment
Labels
question Further information is requested
Milestone

Comments

@joshua-light
Copy link
Member

joshua-light commented Jan 9, 2023

Currently, a custom API reference generator can be build in a separate console application by composing different pipes together. As the time goes, more pipes will be added, hence, we should consider introducing a higher-level API layer (e.g. Pipeline object).

@joshua-light joshua-light added the question Further information is requested label Jan 9, 2023
@joshua-light
Copy link
Member Author

One of the things I'd like to point out is how we should combine common pipe compositions? E.g. a IPipe<string, Doc> is a quite natural pipe that parses specified source code into the document. This pipe can be composed from ParseSyntaxTreePipe and ParseDocumentPipe. Having to always write new ParseSyntaxTree().Then(new ParseDocumentPipe()) is a bit too much (considering the fact that there will be much more pipes and their useful combinations).

@joshua-light joshua-light added this to the Backlog milestone Dec 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant