feat: query modifiers on expand ref are propagated to subquery

[patricebender]

enable the following:

cds.ql`SELECT name, books[order by price] { * } FROM Authors`

it is still possible to have query modifiers defined as sibling property to expand:

{
            ref: ['author'],
            expand: [
              {
                ref: ['name'],
              },
            ],
            limit: {
              offset: {
                val: 1,
              },
              rows: {
                val: 1,
              },
            },
            orderBy: [
              {
                ref: ['name'],
                sort: 'asc',
              },
            ],
          }

--> If both are set, the modifiers in the ref of the expanded association have precedence

[patricebender]

everything covered?

[BobdenOs]

compared with cqn2sql and lgtm.

[danjoa]

👍 but you can take out excluding → that is always next to expand or inline. Also in CQL syntax as supported by the compiler, and hence the CQN produced by it:

cds.ql `SELECT from Authors { ID, name, books[order by title desc limit 1] {*} excluding { descr } }`

⇒ cds.ql {
  SELECT: {
    from: { ref: [ 'Authors' ] },
    columns: [
      { ref: [ 'ID' ] },
      { ref: [ 'name' ] },
      {
        ref: [
          {
            id: 'books',
            orderBy: [ { ref: [ 'title' ], sort: 'desc' } ],
            limit: { rows: { val: 1 } }
          }
        ],
        expand: [ '*' ],
        excluding: [ 'descr' ]
      }
    ]
  }
}