Hey, you will handle this like in a common Angular app: create a service that requests your api and fill the template.
Scully will only request the api to identify all placeholders to find all routes. When running scully it will visit all the route by using the Chrome browser and your angular app built with ng build. The result is stored from scully as static html which can be served and accessed immediately with angular bootstrapping in the background.
Great! Thanks, I’m gonna try that 👍
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.