Considering how configuration scales for larger projects (?)

[bobspryn]

This is point of question or discussion, not a bug. If this isn't the correct spot for it, please close.

I'm interested in Moya, but my initial reaction is that the enum based configuration could quickly get out of hand for larger applications, at which point all the different aspects of a request being handled in very different spots of the file seems potentially awkward.

I have seen https://github.com/devxoul/MoyaSugar which tries to help with this some, but still has the configuration spread out over several different enum methods. Also now we're adding another layer on top of Moya.

Does anyone have experience on using this in larger applications? Is it as awkward as it seems?

[pedrovereza]

I think Artsy's Eidolon should give you an idea of how it looks like in a real product. Here is where their API is defined using Moya.

[bobspryn]

I should have thought to look there. 🤦‍♂️ Thanks @pedrovereza. I'll close this in a bit if I don't have follow-up thoughts.

[bobspryn]

Interesting. So I guess worst case scenario you make a handful of APIs and redefine the base path, etc, in each. Which really could be a shared function somewhere. Not too bad.

[scottrhoyt]

That's the approach I use as well. In order to keep the boiler plate down in the many TargetTypes that I create, I also introduce some defaults for TargetType as seen in #861.

[bobspryn]

Yeah I like the idea @scottrhoyt. Looks like it didn't make the cut though. I'm considering if I can use protocol extensions for now.

[scottrhoyt]

Yep. Just drop something like this in.

[bobspryn]

Solid. Exactly what I was thinking.