Combining static LINQ query with Gridify query

[GlodenBoy]

As in the picture, I need to query x3.state == a.state,

[GlodenBoy]

[alirezanet]

Also, you can combine the static part of your query with gridify.
for example, if the second line in your example is a static query you don't need any mapping for that.

QueryableList.ApplyFiltering( configs ).Where( // your static query) . ToList();

[GlodenBoy]

I actually used Addmap to solve most of the problems, but now this problem is difficult for me, because I want to query the state in the subset of the parent class to determine whether it is equal to the state of the parent class, if I use the passing, then I also need to try to query the state of the current parent class, which must be a very troublesome thing, in linq I only need child.state = main.state

[alirezanet]

That's why I suggested providing a reproducible example 😊. I'm giving you a couple of different ways to solve the problem but not exactly the code you're looking for.

[GlodenBoy]

ok， I'll create a simple example, please wait

[GlodenBoy]

ConsoleApp4.zip
Here is an example

[alirezanet]

So for having the same result as your example there is two way:

example code :

var list = new List<Class1>()
{
	new()
	{
		State = "ok",
		Childs = new List<Class2>()
		{
			new()
			{
				State = "ok",
				UserId = 1,
			},
			 new()
			{
				State = "error",
				UserId = 2,
			}, new()
			{
				State = "error",
				UserId = 3,
			},
			 new()
			{
				State = "error",
				UserId = 4,
			}
		}
	},
	   new()
	{
		State = "error",
		Childs = new List<Class2>()
		{
			new()
			{
				State = "ok",
				UserId = 4,
			},
			 new()
			{
				State = "error",
				UserId =1,
			}, new()
			{
				State = "error",
				UserId = 6,
			},
			 new()
			{
				State = "error",
				UserId = 1,
			}
		}
	}
}.AsQueryable();

//How to convert to Gridify
var get = list.Where(a => a.Childs.Any(x => x.UserId == 1 && x.State == a.State));

internal class Class1
{
	public string State { get; set; }

	public List<Class2> Childs { get; set; }
}

internal class Class2
{
	public string State { get; set; }
	public int UserId { get; set; }
}

---

First, if you want to always map your child State to the parent state you should not use gridify because it is a static hard-coded query:

e.g using query builder

var qb = new QueryBuilder<Class1>()
		.AddMap("child_id", q => q.Childs.Select(c => c.UserId))
		.AddCondition("child_id = 1") // this is your dynamic part
		.Build(list);


// combine your static part
qb = qb.Where(q => q.Childs.Any(c => c.State == q.State)); 

var result = qb.ToList();

---

The second way, if you wanna Control the state:

// get the state from user to control the filtering
var state = "error";

var qb = new QueryBuilder<Class1>()
		.AddMap("child_id", q => q.Childs.Select(c => c.UserId))
		.AddMap("state", q => q.State)
		.AddMap("child_state", q => q.Childs.Select(c => c.State))
		.AddCondition($"child_id = 1, child_state={state}, state={state}")  
		.Build(list);

var result = qb.ToList();

[alirezanet]

I updated the last example,
what do you mean about direct conversion?

something like this?

// Map a single string to multiple different properties
var qb = new QueryBuilder<Class1>()
		.AddMap("child_id", q => q.Childs.Select(c => c.UserId))
		.AddMap("state", new[] { q => q.State,  q => q.Childs.Select(c => c.State) })
		.AddCondition($"child_id = 1, state=error")  
		.Build(list);

This might be possible, Although not sure if it's useful or not.

[GlodenBoy]

No, it's parsing linq queries and converting them into strings recognized by Gridify or QueryBuilder

[GlodenBoy]

The main difficulty above is that state is neither dynamic nor static, it is related to the parent, and I can't pass values unless I associate them when constructing the dataset, but this undoubtedly adds a lot of work, because this is queried from the database, they come from multiple tables, and they are related with primary keys

[alirezanet]

No, it's parsing linq queries and converting them into strings recognized by Gridify or QueryBuilder

Well, could be an interesting feature, but honestly, I'm not sure what problem that string can solve...
maybe with a good proposal/explanation, I add it to the next versions. 🤷‍♂️

[GlodenBoy]

For me strings are better customized than linq, I can send query conditions to the server, let the server query, and then return me the actual result, linq words currently have no particularly easy way to pass