record components are essentially final fields in a class. The contract
is that the order reflects in the record declaration. So i could imagine
that the organize members refactoring could rearrange record components
if it doesn't check for it.
Although there wouldn't be much else to do, outside the occasional
static field I suppose. Might be easy to fix.
-mbien
On 01.02.25 19:51, Patrik Karlström wrote:
When I organize members of a record like
public record Settings(Color borderColor, double borderSize, int width, int
height) {
it changes to
public record Settings(Color borderColor, double borderSize, int height,
int width) {
notice the swap of width & height.
This only happens when a record is in its own file, as a nested object, no
swapping occurs.
I don't see this behavior in NB24.
/Patrik
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
