Vue path #28
Closed
Vue path #28
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'd rather have the configured endpoint in the config explicitly passed through from the controller to the Blade views / vue components. Could you update this PR to work that way? |
|
Sure, but it might take me a bit. I'll close and submit a new PR once I've got that worked out. Thanks! |
This was referenced Aug 26, 2019
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This may not be the best way to do this -- but it worked well for me. Right now the "/tinker" path is easily changable the Larvel config, but hard-coded in the Vue file.
Changing that to "window.location.pathname" should let it work from any path configuration -- or in my case, when Laravel is running in subdirectory. (In that case, the Laravel path setting will not match the POST URL.)