-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Add dataview query inside the field #107
Comments
Please see #103 |
It doesn't explain why there is a glitch I mentioned above, that for good few seconds before the meta-bind button is generated there is just text. |
it seems like the parser has some strange problem with the line breaks in the input field declaration. await dv.paragraph( `${filter}${backticks}${codeblock}${list}):needs]${backticks}`); |
Correction, it seems like dataview is doing some fancy predictive rendering and reactive evaluation of the querry, which reevaluates the script and potentially breaks the input fields |
This is something that dataview does and i have no influence over it, so i can't fix it. |
For example im generating with dataviewJS:
Non of those generate first text and then the GUI. So I think there is something in meta-bind plugin that is doing it. Please check. |
Closing this for now. In the next release, you will be able to build the input field using js. |
I would like to type something like:
INPUT[suggester(
dv.pages().where(b => b.class === 'needs').sort(b => b.date_created, "asc"
)):needs]`This suggester should be filled with filenames coming from this dataview query.
Here is the very tiresome work around with dataviewJS:
But there is a glitch, for good few seconds I see this:
Before the select button renders correctly.
The text was updated successfully, but these errors were encountered: