-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use template needs to work also with starter template #9261
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I searched for additional instances of using extensionsDirectory
and this seemed to be the only one.
This would be I am seeing some occurrences where we externally do the existence-checking quarto-cli/src/extension/extension.ts Lines 694 to 697 in 0ba1c27
quarto-cli/src/extension/install.ts Lines 388 to 393 in 0ba1c27
Looking deeper we do have this helper quarto-cli/src/extension/install.ts Lines 610 to 624 in 0ba1c27
But it was modified not to return Anyhow, I am thinking now that this fix should probably be more scoped to Or I should check all call to |
I went with that, aiming at cleaning some part of our code with some refactoring. |
7143d22
to
74f7fd9
Compare
`quarto use template` can be used to copy files from a remote even if it does not have extension Tweaks from #8764 regarding installation of extension only needs to happen if there is an `_extension` folder
74f7fd9
to
def13d0
Compare
a22388f
to
4d6e132
Compare
4d6e132
to
220f199
Compare
quarto use template
can be used to copy files from a remote even if it does not have extensionTweaks from #8764 regarding installation of extension only needs to happen if there is an
_extension
folder#8764 uses
quarto-cli/src/command/use/commands/template.ts
Lines 83 to 104 in 0ba1c27
This PR makes sure that
readExtensions
returns empty list whenextensionsDirectory
doesn't exists. This should prevent any similar issue when usingreadExtensions
in the future.closes #9256
I did not add to changelog because it was only broken by #8764 merged in 1.5.15