Should we parametrise era in `cardano-wasm` API?

[palas]

Should we keep having methods for different eras? What to do about parametrising algebraic data types in JS?

Proposal:

1. If it we are happy with having two functions (one for current era and one for upcoming), I think it is simpler.
2. The moment we have more than two, or the number of functions is too high, then I would go with "strings". You can specify the literal strings in the types, so it is type safe, and it is simple.
3. If we need more sophisticated algebraic datatypes (nested or with parameters), I would go with objects a la OOP.

[carbolymer]

I would go with "strings". You can specify the literal strings in the types, so it is type safe, and it is simple.

This is a good middle ground between ease of use and type safety IMO. Seems that's also the way to do it in the JavaScript world:

• https://www.geeksforgeeks.org/javascript/enums-in-javascript/
• https://masteringjs.io/tutorials/fundamentals/enum