C#: Blazor: Add route parameters as remote flow sources

[egregius313]

Adds the variables parsed from the @page directive of a Blazor component as remote flow sources

[Copilot]

Copilot reviewed 8 out of 8 changed files in this pull request and generated no comments.

Tip: Copilot only keeps its highest confidence comments to reduce noise and keep you focused. Learn more

[tamasvajk]

LGTM

[hvitved]

Joining on names is always a candidate for a bad join, so it is usually safer to force multi-column joins, e.g.

  pragma[nomagic]
  private Property getAParameterProperty(string name) {
    result = this.getAProperty() and
    result.getAnAttribute() instanceof MicrosoftAspNetCoreComponentsParameterAttribute and
    name = result.getName().toLowerCase()
  }

  pragma[nomagic]
  private string getARouteParameter() {
    exists(string s |
      s = this.getRouteAttributeUrl().splitAt("{").regexpCapture("\\*?([^:?}]+)[:?}](.*)", 1) and
      result = s.toLowerCase()
    )
  }

  Property getARouteParameterProperty() {
    exists(string name |
      result = this.getAParameterProperty(name) and
      name = this.getARouteParameter()
    )
  }

[hvitved]

What is the motivation for using integration tests instead of normal QL tests? I find it quite difficult to run
(specific) integration tests locally...

[egregius313]

This was mostly because the test was originally from Tamás's WIP PR. And I wasn't sure about testing Blazor components as a QL test (I'm unsure if I'll need to have a full project). I'll experiment with moving it.

You are correct about the integration test being a more complicated way to run the test locally.

[hvitved]

If it's not easy to do, then let's do only the integration test.

[hvitved]

Looks like the f.getExtension() = "razor" disjunct can be removed?