Inconsistency in Fluent API Order: Query Composition Bug in URL Generation

[onurkanbakirci]

I have identified an inconsistency when composing queries for URL generation. In my TypeScript code, I observed that the order of the expand and select functions affects the resulting URL, which I believe is unintended behavior.

When I use the following code snippet:

             .expand(
                t => t.class,
                q =>
                  q.select(
                    s => s.id,
                    s => s.name
                  )
              )
              .select(
                t => s.id,
                t => s.firstName,
                t => s.lastName
              )
              .toString()

I obtain the URL: http://localhost:5226/api/v1/teachers?$select=id,firstName,lastName

However, when I switch the order of the functions:

             .select(
                t => s.id,
                t => s.firstName,
                t => s.lastName
              )
             .expand(
                t => t.class,
                q =>
                  q.select(
                    s => s.id,
                    s => s.name
                  )
              )
              .toString()

I get the desired URL: http://localhost:5226/api/v1/teachers?$expand=class($select=id,name)&$select=id,firstName,lastName

This discrepancy suggests that the order of the operations should not affect the result, and I believe this behavior may be a bug. Consistent results should be returned regardless of the order in which expand and select functions are applied.