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
WIP: Project builder improvements #2837
base: master
Are you sure you want to change the base?
Conversation
8e83b24
to
8f96917
Compare
8f96917
to
34298ad
Compare
34298ad
to
d694701
Compare
764d3a3
to
dded9dd
Compare
dded9dd
to
9aa0e52
Compare
@jaapio what is the status of this PR; I am fearful that more incoming changes for the RST parser might influence this PR and it contains a lot of changes |
Please don't care about this PR, I will update it once in a while. Some changes in here are already merged, it was more like a work in progress branch to see where the problems are to start supporting multiple versions. One of the things that came out was the file handling which has been changed. The table of contents changes also found their origin in here. When I have time to pick this one up, I will have to review the changes anyway. |
434077b
to
e527e8d
Compare
to be able to handle multiple api's separate this is a first step towards a more fine grained api parse pipeline. Which will allow us to create multiple documentation sets of different types.
To merge guides in our main workflow I moved the parser into a separate Parser Factory which returns the parser to execute in the parse stage based on the documentation set.
to be able to create some version and project overview we need some templates based on project and version.
ab582cb
to
fb5ac6b
Compare
This PR is here for reference as a POC to be discussed in the core team, feel free to ignore it