Next version

[Roguyt]

I'm currently working on the next version of node-epicsgg.

However a few questions are currently left to debate:

• With the introduction of the streamers should I add back the categoryId flag on every method ?
• I'm working on adding enumerations everywhere (thanks for the suggestion @gjariot) which means we will have a breaking change on the default export of the library.
• What kind of things should I try to include since I'm going for a breaking release anyway ? (such as fix(#40): Fix Collection.seasons interface type #43)

[Roguyt]

cc @SherloxTV & @gjariot now is the time to make requests :-)

[sheerlox]

So the thing I've done in my previous fork was moving the gameId and categoryId in the EpicsGG / BaseClient constructor

[sheerlox]

Enums definitely a great thing indeed

[Roguyt]

I know but I'm not really found of instantiating two instances of the library if I want to work with streamers and csgo at the same time

[gjariot]

• One thing I miss is the meta data in paginated results, such as Market.getListings, the workaround to know whether there's a next page is a bit ugly (we're force to compare the expected number of results with the collection length).
• Maybe propose a generator function that wrap single paginated calls and returns all results to avoid pagination implementation on client side (that's not breaking, just a discussion about the future).
• What would be perfect is to allow to do both of your ideas: a default configuration as we currently have and the possibility to override it on a request basis. That's even not a breaking change, just a functionality.
• I know it's not a production tool, but having the possibility to dynamically get credentials from env variables would be nice.

I see that I have many new features requests (I have others), do you want me to open Issues to discuss them rather than using this one?

[Roguyt]

One thing I miss is the meta data in paginated results, such as Market.getListings, the workaround to know whether there's a next page is a bit ugly (we're force to compare the expected number of results with the collection length).

Sadly I can't do much about it since the only way to know if you need to go to the next page is to verify the length of the returned array

I see that I have many new features requests (I have others), do you want me to open Issues to discuss them rather than using this one?

Keep posting them here and I'll work on it whenever I get some free time

[gjariot]

There's something I'm starting to work on is the sticker handling on market template. This is a breaking change because MarketTemplate interface will change (cardTemplate becomes non mandatory).

May I help you on one of those topics?

[gjariot]

Add a debug mode to the API client to show what url are called, and response time them to enhance 429 tweaking

[Roguyt]

Debug mode is added in the next major release 83e7574