Committed and added a release for that as well
Thanks for the find! That would definitely throw an error in D10, so I have added your patch and made a new release
The notification data is on the notification entity which is the parent entity of the display paragraph - so you should be able to call -> getParentEntity() on the paragraph and then load fields from there. You could probably do that in a preprocess for the paragraphs and add them into the variables for the template
Added patch with additional catches for the other two preg_replace calls - putting them into double quotes is a shorter fix, but it's less readable and can be the cause of weird bugs if the data type changes.
Talking to our team, it sounds like dev have done this before by adding the library to the DMB block, which is not an ideal solution. I think because of how this is loaded attached libraries in the template are likely not working, so this is definitely a bug
That's an excellent point, I'm making this a bug right now. Thank you!
Are there any errors in any logs or console? It looks like it is displaying the notification entity, or at least that it is adding something in there, so I would check the default display of the Notification to make sure you are displaying the paragraphs.
The readme will be changing as D10 updates are merged in, it has already been changed to a markup file. The issue was to change the format, which has already been done. There is no need to merge the code changes as they are outdated.
Please do not re-open this issue.
Sorry, there are a lot of changes upstream for Drupal 10 and this issue will remain closed.
There seemed to be a regression in the regex in patch #72, I have updated it so it applies for 9.5.x and does not break