You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a rather large app with a bunch of different pods under. Right now, I can pass the info in using lazy loading but only the info from the first loaded pod is used. Sounds crazy, right? (We're using Segment for this example)
Why would you do something like that you ask?
Because it would allow us to treat our pods like separate apps all living under the same umbrella with different and distinct tracking information. I'd really hate to have to split all our code into separate apps just to get the tracking info working as described.
I think it would be awesome if I could use the lazy loading technique to override an adapter instance with a new key when loading into a route.
Do you have any suggestions on how to accomplish this?
The text was updated successfully, but these errors were encountered:
We have a rather large app with a bunch of different pods under. Right now, I can pass the info in using lazy loading but only the info from the first loaded pod is used. Sounds crazy, right? (We're using Segment for this example)
Why would you do something like that you ask?
Because it would allow us to treat our pods like separate apps all living under the same umbrella with different and distinct tracking information. I'd really hate to have to split all our code into separate apps just to get the tracking info working as described.
I think it would be awesome if I could use the lazy loading technique to override an adapter instance with a new key when loading into a route.
Do you have any suggestions on how to accomplish this?
The text was updated successfully, but these errors were encountered: