Eugene

I had such helper constructors in my local fork, so it's been requested - I'm making a [PR](https://github.com/jomei/notionapi/pull/185)

@aydinomer00 sync please your branch, so it doesn't have conflicts for merging. I guess then it will be sooner to be merged by maintainer. P.S. I'm ok sitting with local...

hey @aydinomer00. There are several ways of resolving the issue. I don't claim my approach is the most comfortable, but here what you can do: 1. Your fork aydinomer00/notionapi is...

P.S. Here I'd better wait for https://github.com/jomei/notionapi/pull/187 to be merged, and then I'll remove my fixes for `BlockTypeAudio` as there in !187 changes are more complete

Hey. Thanks for a feedback. Let me share details on my motivation behind the provided `promsafe` package. By `err handling nightmare / panics` I meant the following cases: ```go //...

Small update. I've pushed some improvements in API, so it's more consistent and stable. Also, I've update the PR description with cleaner and clearer examples, and added a note on...

> Then there is efficiency aspect I would like to understand, given this is a hot path. There are benchmarks in `safe_test.go`, and here are the results (on a MacBook...

@bwplotka I'd like to continue work on the branch (adding gauge, histogram, tests, etc) soon, so my main blocker is the question: Should I wrap it as *experimental* functionality? If...

> Happy new year! > Hello from 2025 :) Thanks > ... switch metric definitions to... yaml (: OpenTelemetry starts this new pattern with https://github.com/open-telemetry/weaver project ... Thanks for noting...

Hey @bwplotka Considering everything we’ve discussed, I’d like to summarize where we stand. Code generation (e.g., YAML-based) is viable, by existing projects may choose to generate only some metrics or...