# Why would you ever use dot notation over bracket notation?

**URL:** <https://forum.freecodecamp.org/t/why-would-you-ever-use-dot-notation-over-bracket-notation/377330>\
**Category:** Curriculum Help\
**Tags:** javascript\
**Created:** [April 22, 2020, 6:35pm UTC](https://forum.freecodecamp.org/t/why-would-you-ever-use-dot-notation-over-bracket-notation/377330 "2020-04-22T18:35:31Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![ArielLeslie](https://sea3.discourse-cdn.com/freecodecamp/user_avatar/forum.freecodecamp.org/arielleslie/32/264841_2.png) [@ArielLeslie](https://forum.freecodecamp.org/u/ArielLeslie)\
**Post date:** [April 22, 2020, 7:13pm UTC](https://forum.freecodecamp.org/t/why-would-you-ever-use-dot-notation-over-bracket-notation/377330/7 "2020-04-22T19:13:57Z")

</div>

I hadn’t thought about code editors, but now that you mention it - in addition to giving you code completion, in a lot of IDEs you also get the ability to do things like jump to the declaration and get some warnings when you try to access it incorrectly. With bracket notation, editors just trust that you know what you’re doing.

@konstantin.krumin – you’ll always know whether dot notation will “work” when you’re writing the code.

---

_[View the full topic](https://forum.freecodecamp.org/t/why-would-you-ever-use-dot-notation-over-bracket-notation/377330)._
