Leif Åstrand

https://github.com/vaadin/flow/issues/13769 was introduced to deal with issues related to the Vite integration when using a custom servlet path. Based on an internal discussion earlier today, we are leaning towards reverting...

There were also some talks about using a separate bean introspection library instead of the one that is part of the JRE because of the way it requires using lots...

I would assume this is something that could be changed in the actual product so that WebLogic users wouldn't have to do workarounds?

I would suggest that the configuration complexity should be completely moved somewhere else so that we would have a configuration mechanism that would work the same also with Gradle.

Here's some inspiration for what kind of mayhem you can cause with type parameter names that look like regular types: https://horstmann.com/unblog/2022-07-20/index.html

Even though sending binary data in an efficient way means that the request would have to be handled in a slightly special way (multipart), we should probably make sure that...

Even better would be to extract parameter names from JavaDocs in case it's not in the class files, but that's a separate step in addition to just making sure it...

The enhancement label was added by the person who created the issue through using that specific issue template. The team that maintains the code in question hasn't yet triaged the...

Seems to me like your suggestion makes lots of sense. `Long.MAX_VALUE` is `9223372036854775807` which doesn't match that pattern along with roughly 10% of the whole value space of signed 64-bit...

I don't remember exactly what I had in mind in 2016, but I would spontaneously think that it would be resonable to have shorthands for the styles that we see...