Proposal: use ORM for interacting with the database

[Mygod]

Why ORM: less manually written boilerplate code => less likely to make errors. Currently Pokemon populated by DataParser is sometimes incorrect (see also #40). This is partially addressed by #41 but not completely.

I do not have the relevant expertise in this yet but this looks like a promising start: https://medium.com/javascript-in-plain-english/best-orm-libraries-for-javascript-8674c4d49119

Any thoughts on this?

[versx]

I don't have much experience with JS ORM's but I use them in C# and prefer them. Although there's a small performance impact it streamlines a lot of the hassle and reduces boilerplate code imo.

[Mygod]

The performance hit should be minimal. Also we can always optimize later. Personally I just cannot be bothered to look at 600+ lines of boilerplate code in pokemon.js (especially since I cannot attach a debugger) and figure out where the bug is so this would be great. 👍

[versx]

The performance hit should be minimal. Also we can always optimize later. Personally I just cannot be bothered to look at 600+ lines of boilerplate code in pokemon.js (especially since I cannot attach a debugger) and figure out where the bug is so this would be great. 👍

Why can't you attach a debugger? (no devices?)

[Mygod]

Exactly. 😛

(and yes I debug MapJS by staring down the code too)

[versx]

I'll send you a device if you want 👀