fix(api): 'alias' projects (symlinks) should be resolved before checking for 'selfhosted' #934
+7
−5
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.
fixes #933
Projects are marked as an
alias
if they're a symlink, or ifalias:
is matched in the first 1k of of theREADME.md
.Excluding possible errors, the resolved projects are either
valid
(having areleases.js
) orselfhosted
(having aninstall.sh
and local files committed to Webi, no remote releases).Up to this point
alias
projects have simply been cached twice. However,vim-mouse
is a symlink alias ofvim-gui
, which has noreleases.js
and was therefore failing module resolution (as it didn't matchselfhosted
).This change resolves
alias
projects before checking if they'revalid
orselfhosted
.