Skip to content

balls.lua abstract blueprint #2

@insyri

Description

@insyri

Context

The goal for balls.lua is to create a library where all functions are predictable and implementation is swift.

The strafesnet api requires an api key parameter to all calls, passing a key for every function would be doable:

print balls:user("id", "key")
print balls:time("id", "key")
print balls:map_wr("id", "style", "key")

...but there is a better, more simplistic implementation: using classes, or setting a blueprint table to gain inheritance from.


The idea of how the library will look like:

balls.new("key")
balls:some_function("arg1", "arg2")

Every function will either be tied to a specific api call or be a mixture/sugar of two or more functions.

Tracking:

API getters

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationenhancementNew feature or requestin-progressThis is currently being fixed, reviewed, and/or worked on.

Type

No type

Projects

Status

In Progress

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions