Hey all,
Tanner from the product team here! Sorry for the delay in sharing an update.
We’re planning to tackle this in the coming weeks. One approach we’re considering, which would be notably different from the Classic implementation, is exposing resource environments through a custom hook (similar to currentUser()). The goal would be to give you more flexibility in how you implement and use this functionality within your apps.
We’d love feedback on this direction: would a hook-based approach serve your use cases? Are there scenarios where you think it would fall short?
We know this is a critical piece of functionality for many customers and are looking forward to getting a solution into your hands.
P.S. Because testing/qa use cases we’re mentioned, I’m excited to share that we’re also working on a Native Testing feature that should be available for beta testing in early Q4.