Skip to content

Resolve queries instead of hardcoding the path#2416

Merged
koesie10 merged 3 commits intomainfrom
koesie10/resolve-data-extensions-editor-queries
Jun 2, 2023
Merged

Resolve queries instead of hardcoding the path#2416
koesie10 merged 3 commits intomainfrom
koesie10/resolve-data-extensions-editor-queries

Conversation

@koesie10
Copy link
Copy Markdown
Member

This will change the data extensions editor generator to resolve the queries based on the modelgenerator tag. This removes the requirement of having a ql folder in the workspace.

I chose to use the path instead of the id for now to avoid having to resolve the query 4 times. This also avoids the need to map the language names to the language ID in the tag (i.e. csharp -> cs).

Checklist

  • CHANGELOG.md has been updated to incorporate all user visible changes made by this pull request.
  • Issues have been created for any UI or other user-facing changes made by this pull request.
  • [Maintainers only] If this pull request makes user-facing changes that require documentation changes, open a corresponding docs pull request in the github/codeql repo and add the ready-for-doc-review label there.

This will change the data extensions editor generator to resolve the
queries based on the `modelgenerator` tag. This removes the requirement
of having a `ql` folder in the workspace.

I chose to use the path instead of the `id` for now to avoid having to
resolve the query 4 times. This also avoids the need to map the language
names to the language ID in the tag (i.e. `csharp` -> `cs`).
@koesie10 koesie10 marked this pull request as ready for review May 11, 2023 14:16
@koesie10 koesie10 requested a review from a team as a code owner May 11, 2023 14:16
Copy link
Copy Markdown
Contributor

@charisk charisk left a comment

Choose a reason for hiding this comment

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

The code looks good to me but would be good to get 👀 from @starcke on the approach.

Comment thread extensions/ql-vscode/src/data-extensions-editor/generate-flow-model.ts Outdated
@koesie10 koesie10 requested a review from starcke June 2, 2023 10:07
Copy link
Copy Markdown
Contributor

@starcke starcke left a comment

Choose a reason for hiding this comment

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

I think this is ok, and not worse than what we were doing before. Later we should establish some agreement with the maintainers of those queries.

from: qlpack,
queries: ".",
include: {
"tags contain": "modelgenerator",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I wonder how we should ensure that the tag of these are not changed (and that not too many other queries get into this tag). Good enough for now, but lets put a note in the missing functionality doc: https://docs.google.com/document/d/1OoCEtUcShiQG328sPIoS0wNR2pqIg4Umy79UEDiSqLk/edit#heading=h.9b4gwygshmfg

@koesie10 koesie10 merged commit cae7239 into main Jun 2, 2023
@koesie10 koesie10 deleted the koesie10/resolve-data-extensions-editor-queries branch June 2, 2023 11:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants