Update readme to address install challenges #24
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
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.
@groodlooker sorry to bug you, and nice to meet you since our paths at looker didn't cross. You remain a GOAT and I hope your new role is going well!
It appears the google storage endpoint referenced in the README is no longer working, and we've had some customer express confusion about how to get a working install.
This PR updates the Readme to fall back to using vega 3 which appears to work with the existing published artifacts. Let me know if you'd want to take a different approach, but I'm hoping a simple bandaid will work for now.
Really awesome extension, thanks again for making it!