A few usability improvements when using Queries #50
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
…r how the query is being executed (to avoid the UI changing after data has been updated) Change default query to iterate over snapshot instead of use a single console.log, to make results more readable. Fix copy to clipboard to use the full result and not just the first result Also: fix UI to better display multiple results (multiple calls to console.log) by showing them in numbered tabs UI/UX: make UI show a wait animation while running long queries (using the 'loader' class) Firebase: upgrade to latest `firebase-admin` instead of `firebase` version to prevent errors with InitializeApp that is called with wrong parameters.
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.
I had a few issues with the app, so I've created the following changes, hope you'll find them useful:
onoroncefor default queryconsole.logmultiple times. Now it shows eachresultin its own numbered tabinitializeApp()Note: The main reason for my changes was the fact that when using the Queries option against an active production database, the use of
oncaused my query window to keep changing every time the production database changed. Also with long queries, the UI felt frozen because the query happened directly in the ng-click event without allowing the UI to update.