Skip to content

Fix inline query documentation #2462

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

Merged
merged 4 commits into from
Mar 15, 2025
Merged

Conversation

SubsequentlySneeds
Copy link
Contributor

Unless I'm misinterpreting, the current documentation is inaccurate as Inline DQL can query multiple pages. A quick example I tested on the latest version:

image
image

resolves fine despite Blackberry and Lemon being different pages.

Removed this statement from the paragraph.

Current documentation is inaccurate as Inline DQL can query multiple pages.
Removed "either" for clarity since both prefixes can be used in the same IQL query
Copy link
Collaborator

@holroy holroy left a comment

Choose a reason for hiding this comment

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

Based on the current text it now seems like if I wanted to access the file.name, I'd either use this.file.name or [[linkToPage]]file.name. I believe this should be clarified that we indeed need to do [[linkToPage]].file.name in order to access the other page's properties/metadata.

@holroy holroy merged commit 0164e3a into blacksmithgu:master Mar 15, 2025
3 checks passed
Copy link
Collaborator

@holroy holroy left a comment

Choose a reason for hiding this comment

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

It's better, and merged (but still in need of a review?)

Copy link
Collaborator

@holroy holroy left a comment

Choose a reason for hiding this comment

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

Ok

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