Simon Heimler

Just want to give my +1 here. Using [mark.js](https://markjs.io/) did work for me, but it feels like a workaround, because it can only mark already created DOM elements. It would...

Thanks for formulating this @c-pius . I would also consider this a bug, because it (1) is counter to what people will likely expect. And (2) the way it works...

Hi @fmvilas, actually I do like that you've chosen to use a standard for this. The problem is the order of merging beeing done, which is opposite to what you...

@fmvilas yes, I can create a PR to clarify this (just need to find a bit of time for this). Here is a very quick draft, but I didn't have...

I didn't find time to propose the new behavior via PR, but some first ideas and sketches (still hacky and just a basis for further discussion and refinement): * After...

Yes, I also interpreted the JSON Merge patch behavior that arrays get replaced and not merged there as well. This would correspond to the simpler merge algorithm I stated above....

After some fiddling around, I realized that the [`_.merge()`](https://lodash.com/docs/4.17.15#merge) function does also not give the result that I would have expected by default. The issue is that it tries to...

Here is another example for an inheritance use-case (based on @c-pius example) that we can discuss on the AsyncAPI meeting today: ```yaml asyncapi: 2.1.0 info: title: Animals API version: 1.0.0...

And to add a real use-case and not a contrived one: If you use AsyncAPI for describing [CloudEvents](https://cloudevents.io/), there will be some standardized header messages for each event. It would...

No, I totally get you @fmvilas. For a spec it's really important to think this through properly and avoid making rash decisions.