Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

We use this naming convention.

  • All lower case.

  • Prefer short single words if possible

  • Words separated by underscore characters _

Preferred

Instead of

Why

key

password

Better to be consistent with the use of key If we can

organization

Organization

Small case

 Using a single consistent naming convention makes it easier for many customers to learn Iguana

So imagine you read a book that was written in a combination of 5 languages. It might make for an intellectually challenging read but would be difficult for most people to understand.

With Iguana we want our platform to be easily accessible expressing the code using a consistent simple ‘language’ is important. It’s about reducing Bottlenecks for our users to understand how to use Iguana.

Unfortunately this does mean we have to pick a language - we pick English since we are based in North America and this is the defacto global language.

Sorry cannot argue with history.

The naming conventions we favour in Iguana APIs for table parameters.

See Naming conventions.

See Using a table as a function argument

  • No labels