Ben Scholzen

Well, first off, you always only test the matching performance, and completely ignore the instantiation. This is kinda important, since usually for every match you also have the instantiation time...

It breaks even worse with some content, in both Prettier and Biome: [Playground Link](https://biomejs.dev/playground/?code=ZgBvAG8ACgAgACAAPwAgAHsACgAgACAAIAAgAHQAZQB4AHQAOgAgACIAcwBvAG0AZQAgAHIAZQBhAGwAbAB5ACAAbABvAG4AZwAgAHQAZQB4AHQAIgAKACAAIAB9AAoAIAAgADoAIABiAGEAcgAKACAAIAAgACAAPwAgAHsACgAgACAAIAAgACAAIAB0AGUAeAB0ADoAIAAiAHMAbwBtAGUAIAByAGUAYQBsAGwAeQAgAGwAbwBuAGcAIAB0AGUAeAB0ACIACgAgACAAIAAgAH0ACgAgACAAOgAgAHsACgAgACAAIAAgAHQAZQB4AHQAOgAgACIAcwBvAG0AZQAgAHIAZQBhAGwAbAB5ACAAbABvAG4AZwAgAHQAZQB4AHQAIgAKACAAIAB9AA%3D%3D)

@Conaclos It still looks broken, looking at my posted Playground link.

To me it looks like a bug in Prettier. In the given example, the property is indented twice, and the closing bracket is indendet once. I would have expected the...

No, I was referring to [this example](https://biomejs.dev/playground/?code=ZgBvAG8ACgAgACAAPwAgAHsACgAgACAAIAAgAHQAZQB4AHQAOgAgACIAcwBvAG0AZQAgAHIAZQBhAGwAbAB5ACAAbABvAG4AZwAgAHQAZQB4AHQAIgAKACAAIAB9AAoAIAAgADoAIABiAGEAcgAKACAAIAAgACAAPwAgAHsACgAgACAAIAAgACAAIAB0AGUAeAB0ADoAIAAiAHMAbwBtAGUAIAByAGUAYQBsAGwAeQAgAGwAbwBuAGcAIAB0AGUAeAB0ACIACgAgACAAIAAgAH0ACgAgACAAOgAgAHsACgAgACAAIAAgAHQAZQB4AHQAOgAgACIAcwBvAG0AZQAgAHIAZQBhAGwAbAB5ACAAbABvAG4AZwAgAHQAZQB4AHQAIgAKACAAIAB9AA%3D%3D).

@ematipico A quick search yielded a few related ones: - https://github.com/prettier/prettier/issues/4203 - https://github.com/prettier/prettier/issues/12517 - https://github.com/prettier/prettier/issues/5811

I was just about to set up my first cluster and ran into that problem as well. Since we are using GitOps, it's anything but ideal to store the secret...

It is working fine at the moment, because the currently generated SDK does not verify the input parameters. When a newer generator is used (which is planned, see https://github.com/ory/sdk/pull/256#issuecomment-1473892227), the...

Sure, I'll take care of that later tonight. Though what's your opinion on that manual unflattening? It does feel a little bit hacky, we could alternatively use the npm library...

``` bash #!/bin/bash YEAR=$(date +"%Y") for file in $(find . -type f); do sed -i 's/\(Copyright (c) [0-9]\{4\}\)\(-[0-9]\{4\}\)\?/\1-'"$YEAR"'/' $file done; ```