Question. Set custom label om MergeEntity

[tlogik]

Hi.
Is it possible to specify the label and/or labels to use when using the MergeEntity method?

Right now it just gets the typename of the class as label but i would like to decorate with other Neo labels as well.
Is that possible somehow?

example

 foreach (var subject in fbPagePost.Subjects)
                            {
                                var cq = client.Cypher
                                    .MergeEntity(fbPagePost, "fbpost")
                                    .MergeEntity(subject, "subject", labels: new []{"label1", "label2", "label3"})
                                    .MergeRelationship(new RelatesToRelationship("fbpost", "subject"));
                                cq.ExecuteWithoutResults();
                            }

Cheers
Thomas

[simonpinn]

Hi Thomas,

The only way you can set the label to be used is either with the CypherLabelAttribute or the fluent config With<Entity>("label")
You are able to set the labels to "label1,label2" and they will just be passed down to to CQL statement.

It isn't possible to change this at query time. Remember you can always use more than one class to represent a node, so you can always do it by adding a class for the purpose.

I'd also question why you would need to dynamically add a label, use them carefully, you should rarely need to use multiples, at least in my experience.

cheers

Simon

[tlogik]

Hi Simon
The case.
I have many subjects each representing a different kind.
Right now i model using a Subject class.

  public class Subject
    {
        public string Kind { get; set; }
        public string Value { get; set; }
    }

It would be more relevant to be able to store these subject nodes with the Kind as label and then the Value as the only property of the Node.
Then it would be simpler to extract nodes by label.

This label would have to be set on query time.

Is it a design choice of the lib not to support querytime labels?

Cheers
Thomas

[simonpinn]

Hi Thomas,

If they're known "Kinds" then I'd consider modelling each as a separate class with a base class:

public abstract class Subject
        {
            public abstract string Kind { get; }
            public string Value { get; set; }
        }

        public class SomeSubject : Subject
        {
            public override string Kind => "SomeKind";
        }

There has been a discussion about respecting class hierarchy when setting the label, but I've never had the need.

Feel free to raise a PR if it's something you'd like to see 😄

cheers

Simon