Improve naming of external Typescript nodes #260
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.
⚙️ Optimization
[Breaking] Rename
RESOLVES_TO
toIS_IMPLEMENTED_IN
for Typescript modules. The new relationshipsIS_IMPLEMENTED_IN
is much clearer and less generic than the previousRESOLVES_TO
. ForTS:ExternalModule
nodes that match aTS:Module
e.g. because of an identicalglobalFqn
property, it is now straight forward to think of another project using an external module that is also included within the same Graph database as an internal module which actually represents its implementation.Improve naming of external Typescript nodes. Now, an issue is fixed where external declarations were named like their module. Additionally, external modules get a more expressive
name
property in cases where theglobalFqn
looks like one of these examples:Link matching declarations by their names and modules. Now, there is a new
IS_IMPLEMENTED_IN
relationship between external and internal declarations if their names and modules match.Migrate to Miniforge since Mambaforge is deprecated. Details see: Sunsetting Mambaforge
🛠 Fix
📖 Documentation