Bases: Support codeblock Base in callouts

Bug reports
, ,
1

Code-block Bases in Callouts are current broken/unsupported.

2 Likes
2

Description

When modifying a base-from-codeblock that is within a blockquote or callout using the provided GUI, it does not add the required > characters, and then breaks both the blockquote/callout and base codeblock.

Steps to reproduce

  1. Create a new note with a blockquote in it (actual result shown below)
> A blockquote
> With lines
  1. Add a base-from-codeblock into the blockquote (actual result shown below).
> A blockquote
> ```base
> ```
> With lines
  1. Use the GUI to modify the base, e.g. set its type to List (actual result shown below – notice the lack of > characters in the modified lines).
> A blockquote
> ```base
views:
  - type: list
    name: Table
> ```
> With lines

Did you follow the troubleshooting guide? [Y]

Expected result

When doing step 3 (modifying the base), one would expect it to not break, e.g., to make it such that the characters in the markdown file are as follows:

> A blockquote
> ```base
> views:
>   - type: list
>     name: Table
> ```
> With lines

In particular, Obsidian should prepend > (an angle bracket > and a space ) to the lines that it modifies, when the base is within a blockquote.

Actual result

See step 3 – Obsidian does not prepend > and thus breaks the base and quote.

Environment

SYSTEM INFO:
	Obsidian version: v1.10.0
	Installer version: v1.8.10
	Operating system: Windows 11 Pro 10.0.26100
	Login status: logged in
	Language: en
	Catalyst license: supporter
	Insider build toggle: on
	Live preview: off
	Base theme: adapt to system
	Community theme: none
	Snippets enabled: 0
	Restricted mode: off
	Plugins installed: 0
	Plugins enabled: 0

RECOMMENDATIONS:
	none
2 Likes
3

Description

When you have a list-type base-from-codeblock in a callout that is closed by default, and it is showing results whose underlying filesizes are “large enough”, then when expanding the callout from minimized state the list view is empty.

Steps to reproduce

  1. Create a new vault.
  2. Create a folder included, with at least 12 times the free test PDF from https://freetestdata.com/wp-content/uploads/2025/04/15-MB.pdf (12 * 15 = 180MB size total).
  3. Create a new note with a callout that’s closed by default (note contents shown below).
    > [!info]- Callout, closed by default
  4. Add a base-from codeblock that filters such that only the files from included are shown within the callout (note contents shown below).
    > [!info]- Callout, closed by default
> ```base
> filters:
>   and:
>     - file.path.contains("included")
> views:
>   - type: table
>     name: PDFs
>     order:
>       - file.name 
> ```
  5. Change the type of the base-from-codeblock to List (note contents shown below – only change is type: table → type: list).
    > [!info]- Callout, closed by default
> ```base
> filters:
>   and:
>     - file.path.contains("included")
> views:
>   - type: list
>     name: PDFs
>     order:
>       - file.name 
> ```
  6. In reading view, click the arrow of the callout to show its results.

Did you follow the troubleshooting guide? [Y]

Expected result

When “unminizing” the callout, we expect the list view to show the PDFs with combined “large enough” filesize we’ve added to the included folder.

Actual result

The list is empty, see below image:

bug-list-view-in-closed-callout
bug-list-view-in-closed-callout1109Ă—609 12.1 KB

It is important to note that on any change to the files of the vault (a modification to an existing file, a new attachment/file, ..), the list view that is visible in the callout refreshes and correctly shows the items.

Environment

SYSTEM INFO:
	Obsidian version: v1.10.0
	Installer version: v1.8.10
	Operating system: Windows 11 Pro 10.0.26100
	Login status: logged in
	Language: en
	Catalyst license: supporter
	Insider build toggle: on
	Live preview: off
	Base theme: adapt to system
	Community theme: none
	Snippets enabled: 0
	Restricted mode: off
	Plugins installed: 0
	Plugins enabled: 0

RECOMMENDATIONS:
	none
2 Likes
4

I’d like to explicitly mention here that I sincerely hope that codeblock Bases will work in blockquotes/callouts, as all my bases are codeblock bases. Having a codeblock base not feature-equivalent to a non-codeblock base is rather… weird?

=== I’m not allowed to add more comments, so I guess I’ll edit this one ===

And, while I’m at it: my above bug report for that callout-minimize issue persists when embedding a non-codeblock base, e.g.

> [!info]- Callout, closed by default
> ![[test-base.base]]

So @WhiteNoise I believe that this might be slightly more nuanced than “codeblock base in callouts”. Perhaps this comment is enough for tracking purposes; if not, please let me know if a new BR is desired.

1 Like
5

Just adding what I’ve found as I test the bases inside of callouts.

I noticed that when I’m in edit mode, the filters and properties remain as set. But when I change to preview mode, they go back to default.

Not sure what to make of that, but wanted to make a note in the thread.