Add Record and Data classes

[Intybyte]

I used #1028 and #1056 as a base, Data classes are a mutable set of data, whereas record are immutable set of data, many programming language implemented the latter (Java, C#, etc.), the former is less used but still present (POJOs and kotlin's data classes).

Let me know if there are any needed change, or I missed something

[arnaudroques]

Thanks, this sounds like a good idea.

However, I would have used "dataclass" instead of "data class" (for consistency with other type)

Which means change the regex data[%s]+class to dataclass

Does it make sense ?

[arnaudroques]

I may be wrong, but shouldn't we have dataclass here:

"GENDER", "(?:(class|object|interface|enum|annotation|data|record|abstract|[%pLN_.]+|[%g][^%g]+[%g]|\\<\\<.*\\>\\>)[%s]+)*?"), //

[arnaudroques]

Many thanks for your contribution!

If possible, could you also add some basic examples to https://github.com/plantuml/pdiff ? This tool is used to manage non-regression tests.

If you're unsure how to do this, feel free to share your examples here in the thread, we'll be happy to add them to pdiff ourselves.

PS:
I think that this is not needed anymore in LeafType.java

		if (type.startsWith("DATA"))
			return LeafType.DATACLASS;

[Intybyte]

Yeah without a reference I have no idea how to add my references there, however I can show some examples here for record and dataclass in java

These are the java classes:

The java code for the record

public record Key(String namespace, String key) {
    public static final Pattern NAMESPACED_KEY_PATTERN = Pattern.compile("^[a-z0-9._-]+:[a-z0-9._-]+$");

    public Key(String namespace, String key) {
        this.namespace = namespace.toLowerCase(Locale.ROOT);
        this.key = key.toLowerCase(Locale.ROOT);

        if (!NAMESPACED_KEY_PATTERN.matcher(this.full()).matches()) {
            throw new IllegalArgumentException("Invalid NS key: " + this.full());
        }
    }

    public String full() {
        return namespace + ":" + key;
    }

    @Override
    public String toString() {
        return "Key[" +
                "namespace=" + namespace + ", " +
                "key=" + key + ']';
    }
}

To PlantUML

@startuml
record Key {
  - namespace : String
  - key : String
  + {static} NAMESPACED_KEY_PATTERN : Pattern
  + Key(namespace : String, key : String)
  + full() : String
  + toString() : String
}

@enduml

A java POJO (dataclass example)

// lombok data annotation generates setters and getters
@Data public class AngleData {
    private double horizontalAngle;
    private double verticalAngle;
    private double additionalHorizontalAngle;
    private double additionalVerticalAngle;
}

To PlantUML

dataclass AngleData <<lombok>> {
  - aimingPitch : double
  - aimingYaw : double
  - aimingFinished : boolean
  - lastAimed : long
  - timestampAimingMode : long
}

[arnaudroques]

For the record, done here plantuml/pdiff@f2d71d2

[The-Lum]

Hi @Intybyte, @arnaudroques

To anticipate new request...

• Do you have any other keywords evolutions in mind for class diagrams?

Hints:

• Feature Request: abstract entity #1438
• module (and Module System)
• ...

Ref.:

• https://en.wikipedia.org/wiki/List_of_Java_keywords

Regards,
Th.

[Intybyte]

Hi @Intybyte, @arnaudroques

To anticipate new request...

* Do you have any other keywords evolutions in mind for class diagrams?

Hints:

* [Feature Request: abstract entity #1438](https://github.com/plantuml/plantuml/issues/1438)

* module _(and [Module System](https://openjdk.org/jeps/261))_

* ...

Ref.:

* https://en.wikipedia.org/wiki/List_of_Java_keywords

Regards, Th.

I think the module keyword might be useful in the future for adding another layer of abstraction over packages

Also worth considering are sealed classes, though they’d require special handling to define permitted subclasses

[The-Lum]

[Just for the record]

I found (also) this request:

• Add Domain Driven Design "types" to class diagram #2170

Regards,
Th.