How to handle Dyn or Generic Context + Routes

[toadslop]

Let me explain my issue by first describing what I'm trying to do.

1. I have a trait, called DataSource. It's used to define how to fetch data from various backends. For example, I might have a dummy data implementation for testing, a csv implementation for local development, and a postgress implementation for produciton.
2. I want to be able to pass anything that implements this trait into my application so I can switch out where I get my data from
3. I can do by prop drilling when I don't use routes; when I use routes, the view input requires no inputs so prop drillering doesn't work; need to use context. But...
4. I cannot achieve a generic context because I need to use a fake PhantomData input, which causes the router to not compile because it doesn't want any inputs
5. I can't find a way to make a dyn-compatible trait which also satisfies the lifetime requirements of the context api

Is there a straightforward way to achieve what I'm trying to do? If some, Leptos would benefit form having it documented. If there is no straightforward way, it would be nice if a straightforward way could be introduced, whether that's with a wrapper type or an adjustment to the api.

[gbj]

I can't find a way to make a dyn-compatible trait which also satisfies the lifetime requirements of the context api

The answer to the question is Arc<dyn DataSource>. If it's not possible to create an Arc<dyn DataSource> then no, you can't really do this.