Repository navigation
feat: --workspace-root makes published file keys and ids repo-relative - #220
Draft
georgesafta wants to merge 1 commit into
Draft
georgesafta wants to merge 1 commit into
georgesafta wants to merge 1 commit into
Conversation
#219) With --workspace-root, symbol_table keys, module ids and every id below them, and artifact keys/paths/ids are relative to the workspace root instead of --input, matching codeanalyzer-java. The re-key happens at emission only: signatures, entrypoint path rules, test-file detection and the cache keep the input-relative key. --input outside the root is an InputError.
|
@georgesafta , again checking the existing neo4j database case. For typescript, we do have the "--eager" to purge - perhaps should document it and require to use it in case there is data already in neo4j. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation and Context
With
--workspace-root, symbol_table keys, module ids and every id below them, and artifact keys/paths/ids are relative to the workspace root instead of--input, matching codeanalyzer-java. The re-key happens at emission only: signatures, entrypoint path rules, test-file detection and the cache keep the input-relative key.--inputoutside the root is an InputError.How Has This Been Tested?
idandpath.Breaking Changes
There's a new
--workspace-rootoption and theidsand paths are updated when the option is used. When not used the output stays the same as previously.Types of changes
Checklist
Additional context
Related to: #219