Skip to content

qlpacks: libraryPathDependencies -> dependencies#10964

Merged
dbartol merged 3 commits intogithub:mainfrom
smowton:smowton/admin/modernise-qlpacks
Oct 28, 2022
Merged

qlpacks: libraryPathDependencies -> dependencies#10964
dbartol merged 3 commits intogithub:mainfrom
smowton:smowton/admin/modernise-qlpacks

Conversation

@smowton
Copy link
Copy Markdown
Contributor

@smowton smowton commented Oct 25, 2022

This is an initial stab at just removing all references to the deprecated key. I note though that a bunch of these files are named legacy-xyz -- I don't know what these are doing or if they have a reason to use the deprecated key (compatibility with an old codeql?)

RasmusWL
RasmusWL previously approved these changes Oct 25, 2022
Copy link
Copy Markdown
Member

@RasmusWL RasmusWL left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

awesome, thanks 💪 (related PR: #7842)

@erik-krogh
Copy link
Copy Markdown
Contributor

QL-for-QL fails to build because the version of the shared typos pack was bumped, but the version specified in ql/ql/src/qlpack.yml wasn't bumped.
We should somehow ensure that those are kept in sync, but for now you can manually bump the version.

Copy link
Copy Markdown
Contributor

@aeisenberg aeisenberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Certainly all new packs and tests should be using the new syntax.

I'm hesitant to change any of the legacy-support packs (until I learn more about what they are). I would also like to retain at least one test for legacy syntax.

Copy link
Copy Markdown

@dbartol dbartol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please revert all of the changes to the legacy-support packs as discussed in Slack.

Also, I'm assuming that the rest of these dependencies are all to packs in the same repo? If so, then all of the '*' version ranges should be replaced with ${workspace}, which means "whatever version is currently in the same repo". It's not particularly important for query packs, but for library packs that we might eventually publish, it ensures that other consumers of that library pack actually get a compatible version of that dependency.

@smowton
Copy link
Copy Markdown
Contributor Author

smowton commented Oct 28, 2022

Legacy packs reverted; left * alone for now since this is also in use all over the repo, so I'd suggest following up with a different PR rather than broaden this one's scope

Copy link
Copy Markdown

@dbartol dbartol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Copy Markdown
Contributor

@aeisenberg aeisenberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice.

@dbartol dbartol merged commit 85790fc into github:main Oct 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants