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
{{ message }}
This repository has been archived by the owner on May 17, 2021. It is now read-only.
look into a custom blade directive @ignitionjs that adds the entire ignition script, including config. --> This would also lessen the impact on the frontend build process.
The config has the added parameters Vue and applicationPath. The application path is needed because some error stacks resolve their file to a web URL, so adding the application path to the frame's filenames (like in Laravel) will mess up parts of the UI and display incorrect file paths. So it's better to add the application path when opening the editor.
The text was updated successfully, but these errors were encountered:
@mpociot What do you think about this one? Seb and I think it would be pretty neat to be able to use @ignitionjs in a Blade file, which (only in dev mode) would add a couple of lines to get ignition-js from a CDN and initialise it with the existing ignition php config.
Do you think this is something that can be added to the ignition Laravel package?
look into a custom blade directive
@ignitionjs
that adds the entire ignition script, including config. --> This would also lessen the impact on the frontend build process.The config has the added parameters
Vue
andapplicationPath
. The application path is needed because some error stacks resolve their file to a web URL, so adding the application path to the frame's filenames (like in Laravel) will mess up parts of the UI and display incorrect file paths. So it's better to add the application path when opening the editor.The text was updated successfully, but these errors were encountered: