Skip to content

PS: Better usability when working with nested classes#270

Merged
chanel-y merged 4 commits intomainfrom
better-api-graphs
Aug 11, 2025
Merged

PS: Better usability when working with nested classes#270
chanel-y merged 4 commits intomainfrom
better-api-graphs

Conversation

@MathiasVP
Copy link
Collaborator

@MathiasVP MathiasVP commented Aug 11, 2025

@chanel-y mentioned that the following never had any results:

from API::Node n
where
  n = API::getTopLevelMember("system")
          .getMember("security")
          .getMember("cryptography")
select n, "..."

whereas you did have a result with:

from API::Node n
where
  n = API::getTopLevelMember("system.security.cryptography")
select n, "..."

This was somewhat confusing, and I wasn't quite happy with that. So this PR makes it possible to do the former, while also keeping the latter.

While here, I also did some cleanup in the API graph libraries and added some dataflow predicates around models-as-data that i had forgotten to include 🙈

@chanel-y chanel-y merged commit 337132b into main Aug 11, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants