Create a tagged node as a page from table

[hdansou]

Search first

• I searched and no similar issues were found

What Happened?

When adding a node via the tag table, we do not get a page when we press the New button.

Reproduce the Bug

Using the CMD + K to create a new page, with the tag #City, will show the cities on the city tag table.
While on the city tag table, adding a new city node does not create it as a page.
We can verify it by looking for it in the #Page tag table.

Expected Behavior

Page nodes of a given type should all be added the same, with the same type. IF Cities are pages, then they should all be set as pages whether by using cmd + k or the new button on the tag table.

Files

No response

Browser, Desktop or Mobile Platform Information

Logseq version 0.10.10 : 7e89dd3
Microsoft Edge
macOS

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.

• I'm willing to submit a PR (Thank you!)

[logseq-cldwalker]

Hi. Clicking New to create blocks is how tables have been worked since they were first introduced, especially since the Task table relies on this. I've updated https://github.com/logseq/docs/blob/feat/db/db-version.md#tables to be more explicit about this. You could make this an enhancement request but some thought needs to given on supporting a page creation workflow without breaking the existing block workflow. Suggestions welcome

[hdansou]

Thank you for the added documentation.

Here is a recap of my current understanding of when to add a new node(block) or page.

Which result as:

We can see that adding a page via CMD + K looks different.

We can reflect that info in the documentation if the creation compatibility matrix above is accurate.

Regarding the enhancement, adding a new node or page should be clear and done as intended. Users should know what they are getting with the New button.
Additionally, the visual representation of the "thing"(page or block) should be accurate: all pages should look alike.