What should we do with canvases?

[holroy]

Currently the following canvas issues exists:

• Bug Bug report - Inline Query inside Table, inside a canvas node not displaying correctly #2434 Inline query not updating in tables on a canvas
• Feature Support for queries that arrange cards on a canvas #1676 query populating cards on a canvas
• (Closed) Bug Canvas card support #1655 Says inline queries still doesn't work
• Feature file.ext to show .canvas, .pdf etc. #2273 Extend more file extension in queries like .pdf, .canvas, .jpg
• Feature Index .canvas files #1739 Allow indexing of .canvas files, like for markdown --> See PR implement indexing + querying over canvas files #1803 (with changes requested)
• Discussion Can you search for files that are on a specific canvas ? #2023 Can you search for files that are on a specific canvas ?

So now the question becomes, what do we want to implement, and how would that affect other stuff.

Like, I don't believe we should just open up for all extensions, as then we would have a case of file metadata missing on a lot of non-markdown files. Some might be mitigated since users should know when they want to extend queries.

Suggestion: Await this until we've got code block parameters, and then allow extra extensions through an extra parameter.

---

Allowing a query to enter new card onto a canvas? I'm not sure how easy that would be to implement, where would we place them so as not to collide with other elements on the canvas? How would we deal with something like this

---

Bug reports, they need to be triaged, and verified they're still an issue, but we should of course try to fix those.

---

Are there any other canvas issues/features you would like to see implemented/handled? I'm personally not using the canvas functionality a lot, so I'm not good at assesing what's a one time request, or what would be more valuable for the generic crowd. Please add any thoughts or comments on what Dataview should do related to the canvases.