tree faf1422726b040c2ba8da3bd0b39767e69ce6380
parent 0e3cf8f552740a1ed84b0f8a0fd739b4bcf7ba53
author Fabian Meumertzheim <fabian@meumertzhe.im> 1786612923 -0700
committer Copybara-Service <copybara-worker@google.com> 1786612967 -0700

Expand tree artifacts in textual_hdrs in generated module maps (#787)

Tree artifacts in a `cc_library`'s `textual_hdrs` end up in the generated module map as a single `header` entry with the directory's path, which fails to parse (`error: header '<dir path>' not found`), instead of one `textual header` entry per contained file. `hdrs` and `srcs` already expand tree artifacts via the module map action's tree expander; this applies the same expansion to the `public_textual_headers` bucket.

Closes #787

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/787 from fmeum:textual-hdrs-tree-expansion 83f1cf1cb41fce63c6a5c712fe5ba0d610a33036
PiperOrigin-RevId: 963952603
Change-Id: If193b253b0343583c283e3027e5154282afe8139