Skip to content
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.

feat!: monitoring convert to typescript #360

Merged
merged 19 commits into from
Feb 18, 2020
Merged

Conversation

summer-ji-eng
Copy link
Contributor

@summer-ji-eng summer-ji-eng commented Feb 11, 2020

BREAKING CHANGE: generated client in typescript changed the path template helper names

  • deleted js file and add js from generator

  • update package.json

  • correct the path of template in the samples test

  • npm install 👍

  • npm test👍

  • npm run lint👍

  • npm run docs-test👍

  • npm run system-test👍

  • npm run samples-test👍

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Feb 11, 2020
@codecov
Copy link

codecov bot commented Feb 11, 2020

Codecov Report

❗ No coverage uploaded for pull request base (master@ebcc56c). Click here to learn what that means.
The diff coverage is 75.3%.

Impacted file tree graph

@@            Coverage Diff            @@
##             master     #360   +/-   ##
=========================================
  Coverage          ?   76.59%           
=========================================
  Files             ?        8           
  Lines             ?    14628           
  Branches          ?      287           
=========================================
  Hits              ?    11205           
  Misses            ?     3417           
  Partials          ?        6
Impacted Files Coverage Δ
src/v3/notification_channel_service_client.ts 78.89% <ø> (ø)
src/v3/metric_service_client.ts 76.04% <ø> (ø)
src/v3/uptime_check_service_client.ts 75.39% <ø> (ø)
src/v3/service_monitoring_service_client.ts 78.05% <ø> (ø)
src/index.ts 100% <100%> (ø)
src/v3/index.ts 100% <100%> (ø)
src/v3/alert_policy_service_client.ts 74.28% <74.28%> (ø)
src/v3/group_service_client.ts 75.5% <75.5%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ebcc56c...da559f4. Read the comment docs.

package.json Outdated Show resolved Hide resolved
package.json Outdated Show resolved Hide resolved
smoke-test/metric_service_smoke_test.ts Outdated Show resolved Hide resolved
synth.py Outdated Show resolved Hide resolved
@alexander-fenster
Copy link
Contributor

Good news is that system tests pass on Kokoro (that means that the permission denied error is something related to your account setup).

As for samples tests, there are some path templates missing which make them fail. We need to discuss with @xiaozhenliu-gg5 (who knows most about path templates :) ) and see if their omission is indended or not.

@xiaozhenliu-gg5
Copy link
Contributor

xiaozhenliu-gg5 commented Feb 11, 2020

As for samples tests, there are some path templates missing which make them fail. We need to discuss with @xiaozhenliu-gg5 (who knows most about path templates :) ) and see if their omission is indended or not.

this should be fixed by googleapis/gapic-generator-typescript#239

@alexander-fenster alexander-fenster changed the title feat: monitoring convert to typescript feat!: monitoring convert to typescript Feb 12, 2020
@alexander-fenster
Copy link
Contributor

@summer-ji-eng since it has breaking changes now (path template helper names), I changed the title to feat!: ...., it will force our bot to release it as a major version.

@summer-ji-eng
Copy link
Contributor Author

@summer-ji-eng since it has breaking changes now (path template helper names), I changed the title to feat!: ...., it will force our bot to release it as a major version.

Agree. Thanks for reminding.

package.json Outdated Show resolved Hide resolved
Copy link
Contributor

@alexander-fenster alexander-fenster left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with one nit (google-gax version). Thank you!

Copy link
Contributor

@bcoe bcoe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should either try to get onto @JustinBeckwith'[email protected] branch of gts, or add eslint as well for the JavaScript files in the samples directory 👌

otherwise things are looking good to me.

Copy link
Contributor

@JustinBeckwith JustinBeckwith left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly LGTM. I'd like to block on making sure we fix URLs in the upstream monitoring protos and get them synced to third party. If it's broken here, it's broken 7 other times.

package.json Show resolved Hide resolved
package.json Show resolved Hide resolved
package.json Show resolved Hide resolved
synth.py Outdated Show resolved Hide resolved
@summer-ji-eng
Copy link
Contributor Author

summer-ji-eng commented Feb 12, 2020

Mostly LGTM. I'd like to block on making sure we fix URLs in the upstream monitoring protos and get them synced to third party. If it's broken here, it's broken 7 other times.

Thanks Justin, could you show me how to fix URLs or who should I contact to fix URLs?

UPDATE:: Alex showed me how. I will fix the URLs in upstream.

@alexander-fenster
Copy link
Contributor

@summer-ji-eng Can you try adding back the prelint script to make GitHub lint action pass? This is the new CI, the manual and old PRs don't have anything like this.

As for the source protos, I'll show where they are in the chat room.

@summer-ji-eng
Copy link
Contributor Author

we should either try to get onto @JustinBeckwith'[email protected] branch of gts, or add eslint as well for the JavaScript files in the samples directory 👌

otherwise things are looking good to me.

@JustinBeckwith Could you give us suggestion here? Is @2.x.x gtscan catch up linting issues with Javascript, if not, should I add eslint on the top level or just samples directory? Thanks

@JustinBeckwith
Copy link
Contributor

I don't think we want to start messing with gts@2 until we drop support for node 8. Even then, I would prefer we roll it out all at once. Instead, I think we need to:

  • Make sure to add the prelint npm script back
  • Change the fix npm script to "fix": "gts fix && eslint 'samples/**/*.js' --fix",
  • Locally, cd samples && npm install && cd .. && npm run fix
  • Push the changes

I think we were missing the change in the fix script that caused the linter to mess up :)

package.json Outdated
@@ -32,9 +32,16 @@
"samples-test": "cd samples/ && npm link ../ && npm install && npm test && cd ../",
"system-test": "mocha build/system-test",
"test": "c8 mocha build/test",
<<<<<<< HEAD
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that don't look right :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Weird, it doesn't show on my local. The latest commit doesn't contain these "HEAD".

Copy link
Contributor

@bcoe bcoe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is looking good to me; we should make sure before we merge that we clearly document what changes are breaking (that we know of).

change the body of your commit message when squashing to:

BREAKING CHANGE: description of breaking changes.

👍

package.json Show resolved Hide resolved
@alexander-fenster
Copy link
Contributor

@summer-ji-eng Please regen the code once more (run synthtool) because one more change just came in: googleapis/googleapis@56b55aa

It might change the code and we want to include it here.

Copy link
Contributor

@JustinBeckwith JustinBeckwith left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect! Well done 🎉

@summer-ji-eng summer-ji-eng merged commit 5bbd963 into master Feb 18, 2020
@release-please release-please bot mentioned this pull request Feb 18, 2020
@release-please release-please bot mentioned this pull request Feb 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants