Expose supabase types & introduce pretter and eslint #13
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
|
@sduduzog when you are ready, if you can add me as a reviewer and I can take a look. |
|
@scottrobertson I don't think there's a way for me to do so(as a contributor, I believe)... You could however start the review voluntarily... |
|
Oh right... silly Github permissions. In that case, just tag me in a comment in the future when you are ready. Otherwise I end up missing these :D |
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.
We're simply passing on types exported by "vue-supabase" to be available to the user here and introducing eslint and prettier with no specific standard but just for cleaner looking code
supabase-community/vue-supabase#16 closes #11