feat(samples): adds read and filter snippets#586
Conversation
Codecov Report
@@ Coverage Diff @@
## master #586 +/- ##
=======================================
Coverage 87.24% 87.24%
=======================================
Files 33 33
Lines 2046 2046
Branches 373 373
=======================================
Hits 1785 1785
Misses 233 233
Partials 28 28Continue to review full report at Codecov.
|
* feat: add table level IAM policy controls * lint: lint * feat: add instance level IAM policy * docs: update description * docs: add document snippets * lint: lint
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
|
I'm unable to pass lint because of how I am calling the functions |
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) ℹ️ Googlers: Go here for more info. |
bcoe
left a comment
There was a problem hiding this comment.
This is looking good, thanks for working with me and trying out the snapshots.
My only concern, from a stylistic point of view, is that we have been moving towards a single sample per-file (which would have addressed my eval comments). However, I understand the approach you're taking, given that there are many many small methods you're writing samples for ...
tldr; if we move to a switch statement, I'm 👍 on multiple samples in a file.
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) ℹ️ Googlers: Go here for more info. |
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) ℹ️ Googlers: Go here for more info. |
| // [START bigtable_reads_row] | ||
| case 'readRow': { | ||
| const rowkey = 'phone#4c410523#20190501'; | ||
|
|
There was a problem hiding this comment.
Can we delete the unnecessary newlines here?
There was a problem hiding this comment.
I like to separate the variable declarations from the API call, but I deleted the line between the call and print so it would be consistent across the samples
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) ℹ️ Googlers: Go here for more info. |
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #<issue_number_goes_here> 🦕