Skip to content

feat: Remove withComment for codegen#108

Merged
erezrokah merged 1 commit intomainfrom
feat/remove_with_comments
Sep 15, 2022
Merged

feat: Remove withComment for codegen#108
erezrokah merged 1 commit intomainfrom
feat/remove_with_comments

Conversation

@yevgenypats
Copy link
Copy Markdown
Contributor

reading comments from source code is super slow and this is public api which we dont want to support. The best practice/guideline should be just pointing to the original API and not duplicating go documentation to our docs.

Summary


Use the following steps to ensure your PR is ready to be reviewed

  • Read the contribution guidelines 🧑‍🎓
  • Run go fmt to format your code 🖊
  • Lint your changes via golangci-lint run 🚨 (install golangci-lint here)
  • Update or add tests 🧪
  • Ensure the status checks below are successful ✅

@yevgenypats
Copy link
Copy Markdown
Contributor Author

@erezrokah can you please rebase your withUnwrap pr on top of this one once we merged. I want to be super careful with the public api for codegen as users will use it (Yandex already want to convert to this api.)

reading comments from source code is super slow and this is public api which we dont want to support. The best practice/guideline should be just pointing to the original API and not duplicating go documentation to our docs.
@erezrokah erezrokah merged commit d8a5711 into main Sep 15, 2022
@erezrokah erezrokah deleted the feat/remove_with_comments branch September 15, 2022 07:15
This was referenced Sep 15, 2022
kodiakhq bot pushed a commit that referenced this pull request Sep 15, 2022
🤖 I have created a release *beep* *boop*
---


## [0.6.0](v0.5.2...v0.6.0) (2022-09-15)


### ⚠ BREAKING CHANGES

* Remove withComment for codegen (#108)

### Features

* Remove withComment for codegen ([#108](#108)) ([d8a5711](d8a5711))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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.

3 participants