tab-set-code produces warning for code-block

[tcmetzger]

Describe the bug

context
When I use .. code-block:: directives inside of .. tab-set-code::

expectation
I expected the docs to build without warning or error.

bug
But instead I get a warning when running make html: WARNING: All children of a 'tab-code-set' should be a 'literal_block' [design.tab_code]

$ make html

problem
This is a problem because according to the documentation, .. tab-set-code:: should work with .. code-block:: directives, and the (apparently unnecessary) warning is confusing.

Reproduce the bug

In a RST file, include the following:

.. tab-set-code::

    .. code-block:: sh

        cd sphinx

run make html

This gives me the aforementioned warning.

If instead I use:

.. tab-set-code::

    .. literalinclude:: ./snippet.py
        :language: python

I don't get the warning

List your environment

sphinx 5.0.2
pydata-sphinx-theme 0.9.0
sphinx-design 0.2.0
Python 3.10.5
Linux-5.13.0-52-generic-x86_64-with-glibc2.31

[welcome]

Thanks for opening your first issue here! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out EBP's Code of Conduct. Also, please try to follow the issue template as it helps other community members to contribute more effectively.

If your issue is a feature request, others may react to it, to raise its prominence (see Feature Voting).

Welcome to the EBP community! 🎉

[bryevdv]

It looks like this is the relevant check:

sphinx-design/sphinx_design/tabs.py

Lines 143 to 150 in a060931

	if not isinstance(item, nodes.literal_block):
	LOGGER.warning(
	f"All children of a 'tab-code-set' "
	f"should be a 'literal_block' [{WARNING_TYPE}.tab_code]",
	location=tab_set,
	type=WARNING_TYPE,
	subtype="tab_code",
	)

However, the Sphinx CodeBlock directive actually returns a 1-element list with the literal_block inside:

https://github.com/sphinx-doc/sphinx/blob/b9736f23484b16feef86208ab00dd947c54446ba/sphinx/directives/code.py#L169

[tcmetzger]

Seems like this was actually due to me using an incorrectly escaped character - I'm closing this issue as this seems to work correctly. Apologies!