JSON attribute naming convention?

[ramoona]

JSON attribute naming convention?

[ai]

I think “BIN” and “IIN” are internal terms and library users should be able to don’t know them.

Also if ban have 10 BINS like xxxxx[0-9] we can write xxxxx prefix, but it will not be a BIN anymore.

[ai]

Main purpose of brand color is to use it in billing form background. So, at least for library origin purpose, we don‘t need a second color. But of course we are open for use cases :).

[ramoona]

@amio I agree with @ai that prefixes != BIN (or IIN), so we shouldn't rename it. As for colors, I think it may be useful to add something like "colorSecondary", but the main color should stay just "color" ( there's no need to change API :)

[amio]

Also if ban have 10 BINS like xxxxx[0-9] we can write xxxxx prefix, but it will not be a BIN anymore.

Agree with you. Actually I was thinking about shrink some big files with this idea too.

[amio]

@ramoona Sure, a colorSecondary without changing api is good too. :D