Ahhh, yea you're not the first person to ask. I have a colleague that's asked for something similar. I'll add it to the backlog so I don't forget... Just another "Command Pallete Path" ... "Load by app, Load by package" then "Sync record singular" and "Sync Records (by Encoded Query)" where it asks for the table first, and then provides some pre-defined queries? such as "Updated by me" OR "Created/Updated by Me" OR "Created by Me" or "Updated in last hour" or "Custom (paste encoded query)". I would then probably add another command palette option that would let you "Update Pre-Defined Sync Record Queries" where it will ask you to give it a name, define it it applies to a specific table, or "global / all app file tables" and then paste in the encoded query you want to use.. and then that would show up in the queries list.
Also, debating on giving an option to "Load all application files across all tables" based on those query parameters... I like the craziness of this idea, but concerned about the sheer amount of volume that could return and the processing time... It would probably hose an application node for a few minutes (since the API calls I make are multi-threaded). We'll see... maybe i'll add a "Use at your own risk" on it hahaha.
Ahhh, yea you're not the first person to ask. I have a colleague that's asked for something similar. I'll add it to the backlog so I don't forget... Just another "Command Pallete Path" ... "Load by app, Load by package" then "Sync record singular" and "Sync Records (by Encoded Query)" where it asks for the table first, and then provides some pre-defined queries? such as "Updated by me" OR "Created/Updated by Me" OR "Created by Me" or "Updated in last hour" or "Custom (paste encoded query)". I would then probably add another command palette option that would let you "Update Pre-Defined Sync Record Queries" where it will ask you to give it a name, define it it applies to a specific table, or "global / all app file tables" and then paste in the encoded query you want to use.. and then that would show up in the queries list. Also, debating on giving an option to "Load all application files across all tables" based on those query parameters... I like the craziness of this idea, but concerned about the sheer amount of volume that could return and the processing time... It would probably hose an application node for a few minutes (since the API calls I make are multi-threaded). We'll see... maybe i'll add a "Use at your own risk" on it hahaha.