Test is failing due to the transport is named 46elks but classes are named FortysixElks.... Shall I rename the transport to fortysix-elks or alter FrameworkExtensionTest somehow?

@symfony/mergers how do we proceed with the class naming? Thanks

Awesome. Thank you.

Could you add this package to the root composer.json's replace section? I would also like to see fabbot.io happy (just some CS)

About the naming... Hm.. Im not sure. If you dont mind, I suggest to rename the transport to fortysix-elks or similar so the test passes.

Did I understand you correctly about replace @Nyholm?

I made the test pass by ignoring this transport. I think it's a (slightly) better solution than renaming the transport to something that is not the service/company name.

@Nyholm I am not sure about the replace section 🧐

@Nyholm I am not sure about the replace section 🧐

Oh. I was just reading the CI output. I thought we did that for all bridges. See the job

@fancyweb Maybe we did a misstake here?

@OskarStark you are correct. It should not be in the composer's replace section. The CI job was wrong. I've updated the CI job in #44894

Thanks Tobias!

Squashed and rebased. @Nyholm @OskarStark

FortySix or Fortysix
But also 46 or fortysix or forty-six in the package name (and maybe in the service name of course)

If we use letters instead of numbers, that would be FortySix (F and S uppercased), and so forty-six for the package name and where we need underscore names.

In any case, we need to be consistent and only use one or the other, not both.

Renamed classes and transport. Some places still refers to 46elks but that's more about the company rather than the implementation. But some are in between and I'm not sure what to use 🤷

Regarding naming, isn't fortysix-elks more correct than forty-six-elks? It is referring to 46 and not 40 6.

@jongotlin the textual version of 46 is forty-six, not fortysix

@stof, ok thanks. Didn't know.

Thank you @jongotlin.