@Id annotation does not generate required constraint with annotation processor

[shanon84]

Hey there,
if you generate constraints with the annotation processor, an @id annotation only generates a "unique" constraint, but no "required" one. This way it is possible to have nodes without an Id as long as the field is not present on the node. Normally we use the @GeneratedValue annotation too, which prevents it, but if you use custom cypher you can create a node without an id. Is it possible to generate "required" constrain as default for @id annotation too?

Best regards

[michael-simons]

Sure, this is fairly possible.
However, have you thought about using https://github.com/michael-simons/neo4j-migrations/blob/main/extensions/neo4j-migrations-annotation-processing/catalog/src/main/java/ac/simons/neo4j/migrations/annotations/catalog/Required.java ?

Otherwise, I would want to make the processor configurable in that regard… The required constraint is Neo4j enterprise edition only, and I don't want to push this on everyone by default

[michael-simons]

The annotations are dependency free

<dependency>
<groupId>eu.michael-simons.neo4j</groupId>
<artifactId>neo4j-migrations-annotation-catalog</artifactId>
</dependency>

and don't add runtime weight.

[shanon84]

Ah, I see — @required is an enterprise-only constraint. My mistake, I wasn’t aware of that.
In that case, it makes sense not to enforce it universally.
I had considered enforcing the annotation with ArchUnit, but using a processor configuration does seem like a smoother approach.
Honestly, I can't think of a scenario where you'd want an ID field not to be required.