Caleb Cartwright

I think the other point of consideration would be the simplicity factor relative to config and authorization (much of which would have to be reimplemented within the Custom Endpoint model)

Seems like there's some good 3rd party options out there based on what's been shared here, though the more I think about it the more I'm surprised GitHub doesn't have...

Strongly agree with Chris on all fronts. For anyone interested in working on this the starting point in the code would be around here: https://github.com/badges/shields/blob/f53e478b0be6a5f911f7304292640b5d2fa32dee/services/github/github-package-json.service.js#L240-L261

@jNullj wanted to flag your attention in case this was something you'd be interested in working on (definitely no pressure though!)

Appreciate your willingness to jump in @jNullj! I suspect this one probably warrants some discussion first though (e.g. is this something that would be better suited to a [Custom Endpoint...

Thanks for reaching out. I understand you're deliberately obfuscating some of the specifics about your instances, but that's created some ambiguity around what exactly you're trying to do. As such...

I want to be clear up front that I'm **not** arguing _against_ doing this. However, I would like to know what, if any, level of coupling risk exists here. I.e....

That makes sense to me, ty. My impression was that this is/would continue to be a similar paradigm to other parts of the base class hierarchy, e.g. request parameters and...

I'm a little torn on this one. It's a reasonable desire for the message text, but I'm unsure whether it's something we could support natively (without being contradictory to the...

> Could not resolve dependency: npm ERR! peer react@"^16.8.4 || ^17.0.0" from @docusaurus/[email protected] npm ERR! node_modules/@docusaurus/core Well shucks