♻️ Refactor need data post-processing #1018
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR moves the post-processing of needs data into a single event, which takes place before the write phase of Sphinx
In principle, this means that
needs
builders can bypass the entire write phase of the sphinx build.However, there are currently two issues:
export_id
is set on a directive, this requires filter data to also be output in theneeds.json
data, and this is only computed in the write stageneedextract
)needsuml
builder, the data is only added inprocess_needuml