Ben Fradet

@ninjabear @jbeemster any one of you able to help here?

>The concept of passing custom urls also does not seem useful to me I think this is not to have to release a new version if the urls change but...

>if user bought the historical plan, he obviously has access to the history API, but the same api key can be used to access free current/forecast API that's something we'd...

hey, I think this is a blunder on the enhanced-ecommerce's side, wdyt @dilyand ?

Cool thanks, @elliotlings feel free to open a PR for a more relaxed schema :+1:

I have the issue as well, adding a stack trace: ``` #### Error stacktrace: scala.runtime.Scala3RunTime$.assertFailed(Scala3RunTime.scala:8) dotty.tools.dotc.core.Symbols$Symbol.asTerm(Symbols.scala:169) dotty.tools.dotc.core.Definitions.ObjectClass(Definitions.scala:321) dotty.tools.dotc.core.Definitions.ObjectType(Definitions.scala:325) dotty.tools.dotc.core.Definitions.AnyRefAlias(Definitions.scala:424) dotty.tools.dotc.core.Definitions.syntheticScalaClasses(Definitions.scala:2061) dotty.tools.dotc.core.Definitions.syntheticCoreClasses(Definitions.scala:2073) dotty.tools.dotc.core.Definitions.init(Definitions.scala:2090) dotty.tools.dotc.core.Contexts$ContextBase.initialize(Contexts.scala:882) dotty.tools.dotc.core.Contexts$Context.initialize(Contexts.scala:504) dotty.tools.dotc.interactive.InteractiveDriver.(InteractiveDriver.scala:41) scala.meta.internal.pc.MetalsDriver.(MetalsDriver.scala:30) scala.meta.internal.pc.ScalaPresentationCompiler.newDriver(ScalaPresentationCompiler.scala:101) #### Short summary:...

Better yet would be to split uuid-based requests from vendor prefix-based requests: - On the one hand, you would have: ``` /api/apikeys/keys/some-uuid ``` For retrieving the vendor prefix associated with...

A vendor prefix can have at most two (read and write) api keys and obviously an api key can only have one vendor prefix

Ok thanks for your input.

Noted, will do.