You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Potential fix by adding a priority allows to push collecting diagnostics to the back:
Yes, it certainly makes sense to have the sphinx_agent do its thing last - feel free to open a PR tweaking the priority if you'd like.
If not, I can do it when I switch back to working on esbonio in the next few weeks (currently focusing on updating esbonio to pygls v2.0a2, which requires I do some work in https://github.com/swyddfa/lsp-devtools first)
Expected behavior
I'd like to have sphinx-needs warnings available in esbonio 1.0
Actual behavior
Warnings from sphinx-needs are NOT available in esbonio 1.0
Analysis
sphinx-needs
writes diagnostics data uponbuild-finished
event.sphinx_agent
collects diagnostics data uponbuild-finished
event.Unfortunately they do it in incorrect order.
sphinx_agent
syncs diagnostics and THENsphinx-needs
generated diagnostics.Links:
esbonio/lib/esbonio/esbonio/sphinx_agent/handlers/diagnostics.py
Line 48 in f1ec7fc
I did not look into:
Potential fix by adding a priority allows to push collecting diagnostics to the back:
app.connect("build-finished", sync_diagnostics, priority=999)
The text was updated successfully, but these errors were encountered: