Jason Field

Thanks for the criteria @gal-legit, I think it's very solid. My initial idea was to have a separate function to call to have it auto handle pagiantion, similar to how...

So I know I've been poor at responding on this. So far I'm testing the latest iteration of paginatiors I've made which looks like the below. Still need more tests...

that's what I'm thinking, making it an external repo people can use and then a conversation about joining it into the main repo in future when go 1.18 is the...

Repository is up now: https://github.com/xorima/go-api-pagination note: the repo itself may be moved in a few weeks while I go through some work processes to have it as part of the...

Fantastic @danielhochman I've also finally moved my variant to the final location: https://github.com/hsbc/go-api-pagination @gmlewis are you happy for an update to the readme pointing to the two different pagination handler...

Yep, my other thought is the same secret could be used by multiple apps requiring different names. While yes a different secret for each would be better we all know...

So my ultimate fix for this was to stop using the 1password operator and start using ExternalSecrets as their onepassword integration is better than 1password's integration

Hey @tomwilkie Any updates on the versioning? Even if we just cut a manual for now it would be a great help ❤️

Thanks @rgeyer So I'm interested in a versioning system, but by manual release I mean more cut a `v0.1.0` tag, and then using `go install` people can at least install...

Hey @rgeyer / @tomwilkie any updates on this? If I pop in a pr which will handle versioning for you via github actions would this work for now or do...