Skip to content
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

Update link to Message definition in spec #937

Merged
merged 1 commit into from
Sep 19, 2023

Conversation

hasheddan
Copy link
Contributor

@hasheddan hasheddan commented Sep 18, 2023

Fixes broken links to cloudevents spec.

Signed-off-by: Daniel Mangum georgedanielmangum@gmail.com

@embano1
Copy link
Member

embano1 commented Sep 18, 2023

Hello Sir :)

Do you mind going through the repo and fix the other occasions as well? Would be awesome.

Quick grep I did (please verify)

grep -lir master .
./test/sql/shortcircuit_test.go
./docs/concepts.md
./binding/format/protobuf/v2/pb/cloudevent.pb.go
./binding/format/protobuf/v2/pb/cloudevent.proto
./.gitmodules
./README.md
./v2/binding/encoding.go
./v2/event/eventcontext_v03.go
./sql/v2/parser/case_changing_stream.go
./sql/v2/README.md
./sql/v2/CESQLLexer.g4

Copy link
Contributor Author

@hasheddan hasheddan left a comment

Choose a reason for hiding this comment

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

@embano1 sure thing!

@hasheddan
Copy link
Contributor Author

@embano1 a number of the refs from your grep are versioned links that are not broken so I opted not to update those -- however, this PR does now fix all broken links.

@@ -7,7 +7,7 @@
package pb

import (
any "github.com/golang/protobuf/ptypes/any"
any1 "github.com/golang/protobuf/ptypes/any"
Copy link
Member

Choose a reason for hiding this comment

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

did you make those changes intentionally?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

these were automatically made as part of generation -- I installed the matching versions of protoc and protoc-gen-go as detailed at the top of this file. I would imagine these changes were made automatically because I have a newer version of go installed locally (go1.20.7) and the any alias conflicts with the any keyword. I'm happy to generate with 1.17 if preferred, though it might be desirable to go ahead and update these.

Copy link
Member

Choose a reason for hiding this comment

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

Yeah, we're still including 1.17 to make sure older versions of Go can use the SDK/we don't accidentally start using >go1.17 features (until we decide to bump).

IMHO the any1 is not a breaking change here, but if you don't mind please re-gen with 1.17 so we don't introduce this change?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

IMHO the any1 is not a breaking change here, but if you don't mind please re-gen with 1.17 so we don't introduce this change?

Sounds good, will do!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done 👍🏻

Copy link
Member

Choose a reason for hiding this comment

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

do we need that?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

whoops definitely not!

Fixes broken links to cloudevents spec.

Signed-off-by: Daniel Mangum <georgedanielmangum@gmail.com>
Copy link
Member

@embano1 embano1 left a comment

Choose a reason for hiding this comment

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

Thx a ton!

@embano1 embano1 enabled auto-merge September 19, 2023 13:37
@embano1 embano1 merged commit 98443b8 into cloudevents:main Sep 19, 2023
8 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants