Why is a power up necessary for custom fields?

[Christoph Pichlmann]

As the title says.

The documentation even boasts that the custom fields are now part of the API, which is true in a way, but compeletely useless all the same.
Being part of the API is no good if it's locked. Might as well not be part...

Also, completely off-topic - why is it so hard to add tags? Go into field, add text, go out of field, go back, enter text, etc...

[Iain Dooley]

@Christoph Pichlmann yeah it's a little weird that custom fields, calendar and voting are powerups because they are kind of trello features and have special places in the API. But regardless I don't think it's true that they might as well not be part of the API. 

In Trellinator, the way I handle the fact that custom fields may not be enabled when creating code is just to enable custom fields if it's not enabled, and create a custom field if I try to set one and it doesn't exist, throwing an exception if there are too many power ups (ie. if they don't have business class and they're already running one power up).

Here are the relevant bits of code:

https://www.theprocedurepeople.com/trellinator-automate-trello/docs/trellinator-libs_Board.js.html#line582

https://www.theprocedurepeople.com/trellinator-automate-trello/docs/trellinator-libs_Card.js.html#line1247

https://www.theprocedurepeople.com/trellinator-automate-trello/docs/trellinator-libs_Card.js.html#line1338