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

doc: follow common readme guidelines #58

Merged
merged 5 commits into from
Jul 24, 2023
Merged

doc: follow common readme guidelines #58

merged 5 commits into from
Jul 24, 2023

Conversation

gagbo
Copy link
Member

@gagbo gagbo commented Jun 16, 2023

Description

README glow up.

Checklist

  • The CHANGELOG is updated.
  • The open-telemetry example in repository works fine:
    • the docker compose file is valid
    • the application compiles and run
    • alerts are getting triggered in Prometheus
  • The prometheus example in repository works fine:
    • the docker compose file is valid
    • the application compiles and run
    • alerts are getting triggered in Prometheus
    • exemplars are accessible on the graph

@gagbo gagbo force-pushed the doc/readme branch 12 times, most recently from 3f576a8 to a462414 Compare June 21, 2023 12:33
Shadowing constants in function bindings should be a compilation error
(and is, in Rust), but it's not here.

Also changing the names of constants to add extra words and type suffix
to hopefully avoid conflicts later.
README.md Outdated
[![Discord Shield](https://discordapp.com/api/guilds/950489382626951178/widget.png?style=shield)](https://discord.gg/kHtwcH8As9)

Metrics are a powerful and cost-efficient tool for understanding the health and
performance of your code in production. But it's hard to decide what metrics to
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
performance of your code in production. But it's hard to decide what metrics to
performance of your code in production, but it's hard to decide what metrics to

README.md Outdated

See [autometrics.dev](https://docs.autometrics.dev/) for more details on the ideas behind autometrics.

**Table of Contents**
Copy link
Member

@mellowagain mellowagain Jul 24, 2023

Choose a reason for hiding this comment

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

toc is integrated in the github ui already

image

image

README.md Outdated

There is a one-time setup phase to prime the code for autometrics. Once this
phase is accomplished, only calling `go generate` is necessary.

### Install the go generator.
#### 1. Install the go generator.
Copy link
Member

Choose a reason for hiding this comment

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

i wouldnt go from # to ####, maybe do like # to ### (it looks weird in the toc generated by gh, see comment above)

README.md Outdated
```patch
+//autometrics:inst
-func AddUser(args interface{}) error {
+func AddUser(args interface{}) (err error) {
Copy link
Member

Choose a reason for hiding this comment

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

go 1.18 renamed interface{} to any, we should prefer that instead of relying on the alias: https://stackoverflow.com/a/71964388/11494565

@gagbo gagbo merged commit b297955 into main Jul 24, 2023
7 checks passed
@gagbo gagbo deleted the doc/readme branch July 24, 2023 11:38
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