Postgres Realtime Querying hydration and commonality to postgREST

[Towerful]

Hello,
I would love to see some better hydration options for Postgres Realtime.
Would it be possible for a successful connection to also return an initial data set?

Alternatively, is there a way to use the supabase-js query builder to return the RealtimePostgresChangesFilter object?
so supabase.from('users').select('name').eq('id', 1).toRealtime('*') might return {event: '*', schema: 'public', table: 'users', filter: 'id=eq.1'}
This would allow something like:

const query = supabase.from('users').select('name').eq('id', 1)
const subscription = supabase.channel('client').on('postgres_changes', query.toRealtime('*'), payload => {
    // ...
})
const { data, error } = await query

or, perhaps, the result of the await-ed query would have an additional realtime property that would include the information. e.g

const result = await supabase.from('users').select('name').eq('id', 1)
const subscription = supabase.channel('client').on('postgres_changes', result.realtime, payload => {
    // ...
})

---

I realise that this breaks down when dealing with multiple relations and complex queries.
Using the 2nd method above (after a successful query) might allow for auto-generation of multiple realtime filters, however the complexity would very quickly explode.
It might work like this:

const result = await supabase.from('users').select('*, posts ( * )').eq('id', 1)
const subscription = supabase.channel('client')
    .on('postgres_changes', result.realtime.users, payload => {
        // {event: '*', schema: 'public', table: 'users', filter: 'id=eq.1'}
    }).on('postgres_changes', result.realtime.posts, payload => {
        // {event: '*', schema: 'public', table: 'posts', filter: 'user_id=eq.1'}
    })

---

perhaps a better way would be to allow the postgREST client to execute arbitrary strings.
So the id=eq.1 that is required for Realtime can also be used by postgREST.

const filter= `id=eq.${userId}`
const result = await supabase.from('users').select('*').raw(filter)
const subscription = supabase.on('postgres_changes', { event: '*', schema: 'public', table: 'users', filter }, payload => {
    // ...
})

this would certainly be the easier one to implement in the short term, and would reduce the duplication of logic