More stable way to generate node documentation links #4727
Merged
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.
Addressed problem description
Node modules categories and node documentation categories are not 100% consistent. So there was magical conditions to translate the modules categories to docs ones. I reconsidered the approach and now categories does not take part in search of node documentations. It's completely based on the module names and it means that all node modules should have uniq names (even if they are in differen folders).
Also, now all nodes implement new method:
This method should be overridden by Sverchok's extensions if they want to use links to node documentations.
New way reviled two nodes which does not have documentation and were not marked as known problems:
Preflight checklist