-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: move things around #241
Conversation
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.
Only some small concerns are commented, but overall it looks great, and it's really helpful to make the code more readable and cleaner, thanks @alexander-fenster !
npm install | ||
npm test | ||
npm run fix | ||
npm run compile | ||
npm run system-test | ||
npm run docs | ||
npm run docs-test |
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.
Is this intentional to remove docs-test
?
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.
Yes. I think it does not make sense to check if links in the generated docs are valid because if they are not, it's more likely not a generator failure. We disabled this check for DLP and might also want to disable it for monitoring, which probably means it's better to disable it for all libraries.
@@ -3,7 +3,7 @@ google/protobuf/descriptor.proto | |||
google/api/annotations.proto | |||
google/protobuf/duration.proto | |||
google/protobuf/timestamp.proto | |||
google/kms/v1/resources.proto | |||
google/cloud/kms/v1/resources.proto |
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.
I'm a little bit confused here, if we generated google/kms/v1/resources.proto
before instead of /google/cloud/kms....
in proto_list, that sounds like a bug?
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.
Originally kms
lived in protos/google/kms
, I just moved it to protos/google/cloud/kms
to match the googleapis location.
@@ -7,8 +7,5 @@ | |||
}, | |||
"include": [ | |||
"typescript/**/*.ts" | |||
], | |||
"exclude":[ | |||
"typescript/test/test_application_ts/src/*.ts" |
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.
i'm not sure the reason why we excluded the file in the tsconfig here, if it's safe to remove it?
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.
Because it's now outside of typescript
folder (it's a fixture, so it's in fixtures).
@@ -0,0 +1,137 @@ | |||
// Copyright 2020 Google LLC |
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.
This looks great, much cleaner to have a separate file for code map!
describe('Baseline tests', () => { | ||
initBaselineTest(); | ||
|
||
runBaselineTest({ |
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.
This template is so cool, thanks for doing this!
d797935
to
0a62164
Compare
0a62164
to
13eb629
Compare
In this PR I'm moving a lot of things around to achieve the following goals:
circleci.yml
typescript/
folder contains only*.ts
files, fixtures and protos moved out