Mangle generated composition IDs for use in `${topic:<ID>}`

[x1B]

Currently, a hard-to-interpret validation error is raised when trying to generate topics from within a composition whose ID (usually based on the filename) is not a valid topic.

We might want to generate appropriately mangled topics or at the very least give a better explanation.

[jpommerening]

@x1B, @alex3683: I think we're currently trying to make the part that is generated from the name camel case, but we're appending an auto-incremented id separated by a -, like -id123. We could replace that with a +…

I'd love to fix this before releasing the next patch release, but only if we can come to a decision quickly ;)

[x1B]

Hmmm, ofc this might break automated tests :/

[jpommerening]

Oh, you mean tests in dependent projects? Yeah … that's … unfortunate.

[x1B]

@jpommerening To fix this in a minor, could we add a laxar.config.js option?

Then we could deprecate the current behavor in an upcoming minor, and drop the config in the next major.

[jpommerening]

@x1B: Ah, that's a wonderful idea! Except we'd have to update laxar-loader as well to pass the config to artifactValidator.create().

[jpommerening]

Ok, let's keep that for next year. Don't want to break something now, just because of my impatience. 🤓

[alex3683]

@jpommerening @x1B Sorry for my late reply (at least I still answered this year :-)).
Is the -really the problem? I thought that was a valid part of a topic ... Wouldn't we have had a problem with this much earlier?
Sadly I cannot recall the actual bug we had.