-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
fix: Renaming region tags to not conflict with documentation snippets #834
Conversation
…t with documentation snippets
Codecov Report
@@ Coverage Diff @@
## master #834 +/- ##
=======================================
Coverage 99.22% 99.22%
=======================================
Files 18 18
Lines 17416 17416
Branches 1025 1025
=======================================
Hits 17281 17281
Misses 132 132
Partials 3 3
Continue to review full report at Codecov.
|
Docs snippets seems to be failing just because I moved the api reference docs, but should be fine once code is submitted |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this mean we'll have essentially the same samples in two places? wondering if we could just retire the other samples and have their home be in this repository (this is what we've done for some other libraries).
Potentially yes, but currently these samples were written with the intent for just the API reference docs, not for the cloud site documentation. Right now there are some duplicated samples, and ideally these samples are the same in both places, but I'm trying to separate them for easier indexing by the samples tracker. I'm not really sure what other products do for this, but I know I have the same issue in python |
🤖 I have created a release \*beep\* \*boop\* --- ## [3.3.0](https://github.com/googleapis/nodejs-bigtable/compare/v3.2.0...v3.3.0) (2021-03-08) ### Features * add CMEK fields ([#845](https://github.com/googleapis/nodejs-bigtable/issues/845)) ([0381fb7](https://github.com/googleapis/nodejs-bigtable/commit/0381fb7da68492b85f8a3359d5fb97ca4898810e)) * introduce style enumeration ([#833](https://github.com/googleapis/nodejs-bigtable/issues/833)) ([99b7617](https://github.com/googleapis/nodejs-bigtable/commit/99b7617e215126fc36ef3c3ebefb244e0d8d2242)) * **protos:** update BigtableTableAdmin GetIamPolicy, change DeleteAppProfileRequest.ignore_warnings to REQUIRED ([59a0d26](https://github.com/googleapis/nodejs-bigtable/commit/59a0d269d5196991dd395e671d7d5f54ce449005)) ### Bug Fixes * **browser:** check for fetch on window ([#824](https://github.com/googleapis/nodejs-bigtable/issues/824)) ([a38cbcc](https://github.com/googleapis/nodejs-bigtable/commit/a38cbcca1660bc40fe137acb973bf62f3c55754e)) * Renaming region tags to not conflict with documentation snippets ([#834](https://github.com/googleapis/nodejs-bigtable/issues/834)) ([5d3e8f7](https://github.com/googleapis/nodejs-bigtable/commit/5d3e8f721c2a32a33bf41baa1ed237fb90f7cbd6)) * **retry:** restore grpc_service_config for CreateBackup and RestoreTable ([#851](https://github.com/googleapis/nodejs-bigtable/issues/851)) ([3ff2828](https://github.com/googleapis/nodejs-bigtable/commit/3ff282855f4f9a52a89bca8d087c1423e71bd7c6)) * set keepalive configuration ([#836](https://github.com/googleapis/nodejs-bigtable/issues/836)) ([8105dea](https://github.com/googleapis/nodejs-bigtable/commit/8105dea272de44e69915d3e62e5b5add106b54cb)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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> 🦕