Ok, this actually looks cleaner and more concise. I'm assuming from this that the virtual property relation to users is setup automatically because both entities exist in one context. I'm puzzled by how this really works
Here's another strange thing I'm picking up from this snippet, the fact that the property name and its type can just be exactly the same without C# complaining. I've been experimenting areas where such is possible. public virtual Token Token;
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great! Now try lambda expression, you will be happier:)
I did 😅 it looks way better if you're working on a single table
You can use navigation properties and lambda to improve your code.
Something like:
public class User
{
public virtual Token Token { get; set; }
}
And then:
_context.Users.SingleOfDefault(u => u.Token.Body == Token);
Ok, this actually looks cleaner and more concise. I'm assuming from this that the virtual property relation to users is setup automatically because both entities exist in one context. I'm puzzled by how this really works
Here's another strange thing I'm picking up from this snippet, the fact that the property name and its type can just be exactly the same without C# complaining. I've been experimenting areas where such is possible.
public virtual Token Token;