Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Naming - DynamoDb -> DynamoDB

See original GitHub issue

Spotted this difference and can’t unsee 😃

In AWSSDK, DynamoDB with a captial B is used in all types, namespaces, docs etc. To be consistent, consider following the vendor’s naming.

Issue Analytics

State:
Created 2 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

damianhcommented, Apr 20, 2021

As I said, not a hill 😉

Close as discision made.

0reactions

firenerocommented, Apr 20, 2021

@damianh It’s a controversial topic indeed. I guess it’s more like a personal taste than a real difference. I agree with @lezzi that 3 sequential uppercase characters are harder to read/write.

If I have both AWSSDK.DynamoDB2 and this package reference in the same project, one will have to deal with the mixed casing of the name.

It’s a tradeoff we had to make. On the other hand, if we keep naming the same, one will have to deal with different imports and it would be impossible to know what library is used just by looking at attributes. You would have to check imports all the time.