Alert content block in VAMC detail page not showing on front end if the Alert heading field is empty

[xiongjaneg]

Issue description

The Alert content block doesn't show when published on Veteran-facing site if the Alert heading field is empty. It shoudl be required, but we can't make it required until we have a means of toggling between the reusable vs not reusable block.

See in demo environment that the Alert heading is empty demo link

On the preview page, the alert isn't showing preview link

See Jira issue

[kevwalsh]

I could be wrong (and i don't have the context for this issue, which could be helpful), but i believe we used to support an alert that had been designed without a heading. If that support needs to continue, then this is a FE issue. (although we could stand to improve our guidance). If the heading should be required, the FE work to remove its dependency on it, while ideal, is less of a priority, as we can simply make it required.

I'm adding VAMC and Benefits Hubs, as those are the two products affected by this.

[xiongjaneg]

@kevwalsh This came up because a VAMC editor working on a detail page tried adding an information Alert content block but it didn't show on the front end. In staging, I added a title to the alert and then it showed on the front end for me. I ended up recommending he use the alert field instead of the content block anyway, because it it looked better.

The bigger question for me is why is there an alert content block? Shouldn't the editor used the better formatted alert field?

[xiongjaneg]

tested in staging, alert shows on preview if there is an Alert Heading, doesn't show on preview if there isn't an Alert Heading, couldn't replicate editor's issue (alert not showing even though he put an Alert Heading)

[xiongjaneg]

Slacked Michelle for FE issue, waiting for issue number

[xiongjaneg]

FE issue #29771