[3.x] Remove unnecessary Ziggy parameter which causes ESLint errors #1347
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using the additional
Ziggy
parameter with.use(ZiggyVue, Ziggy)
is unnecessary when using the@routes
Blade directive. Leaving this in (accurately) triggers an ESLint errorESLint: 'Ziggy' is not defined.(no-undef)
sinceZiggy
is undefined in this context.Since this additional parameter isn't necessary as the
@routes
blade directive is already being used, it should be removed to avoid triggering errors when using ESLint.Alternatively, we could add
const { Ziggy } = window
or change the parameter towindow.Ziggy
, but this is all unnecessary and removing it seems to be the simplest, cleanest solution.See Ziggy Docs for more information