Timeline for How do I declare a namespace in JavaScript?
Current License: CC BY-SA 3.0
52 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 12, 2022 at 13:08 | answer | added | KyleMit ♦ | timeline score: 2 | |
| Sep 24, 2021 at 9:25 | answer | added | Pavel Chuchuva | timeline score: 6 | |
| Jul 4, 2021 at 18:10 | comment | added | Sebastian Simon | Meh, nowadays we have symbols and modules, so duplicate namespaces shouldn’t even be an issue. | |
| Dec 16, 2019 at 16:06 | answer | added | vishu2124 | timeline score: -1 | |
| Jul 5, 2018 at 11:41 | answer | added | Yairopro | timeline score: 6 | |
| Mar 22, 2017 at 12:27 | answer | added | ttt | timeline score: 17 | |
| Jan 31, 2017 at 16:06 | answer | added | Divyanshu Rawat | timeline score: 19 | |
| Nov 28, 2016 at 0:05 | answer | added | ziesemer | timeline score: 10 | |
| Oct 20, 2016 at 11:43 | answer | added | Saurabh tiwary | timeline score: 1 | |
| Jan 20, 2016 at 17:43 | answer | added | nomæd | timeline score: 3 | |
| Aug 21, 2015 at 5:23 | answer | added | ganesh | timeline score: 1 | |
| Jun 13, 2015 at 4:31 | answer | added | kungfooman | timeline score: 1 | |
| Apr 16, 2015 at 13:38 | answer | added | Spooky | timeline score: 0 | |
| Feb 4, 2015 at 22:45 | answer | added | Razan Paul | timeline score: 8 | |
| Dec 2, 2014 at 15:39 | answer | added | haxpanel | timeline score: 2 | |
| Oct 12, 2014 at 10:14 | history | protected | Tushar Gupta - curioustushar | ||
| Aug 29, 2014 at 16:20 | history | reopened | George Stocker | ||
| Aug 29, 2014 at 16:19 | history | edited | George Stocker | CC BY-SA 3.0 |
added 49 characters in body
|
| Aug 13, 2014 at 3:41 | review | Suggested edits | |||
| Aug 13, 2014 at 3:48 | |||||
| Sep 9, 2013 at 21:11 | review | Reopen votes | |||
| Sep 9, 2013 at 21:18 | |||||
| Sep 9, 2013 at 16:00 | review | Reopen votes | |||
| Sep 9, 2013 at 16:06 | |||||
| Sep 8, 2013 at 15:59 | review | Reopen votes | |||
| Sep 8, 2013 at 16:02 | |||||
| Sep 7, 2013 at 15:58 | review | Reopen votes | |||
| Sep 7, 2013 at 16:03 | |||||
| Sep 6, 2013 at 15:56 | review | Reopen votes | |||
| Sep 6, 2013 at 15:57 | |||||
| Sep 5, 2013 at 15:55 | review | Reopen votes | |||
| Sep 5, 2013 at 15:57 | |||||
| Jul 19, 2013 at 5:12 | comment | added | Justin | This is a ton of information, but really lays out the differences amongst the different JS design patterns. It helped me a lot: addyosmani.com/resources/essentialjsdesignpatterns/book | |
| Nov 15, 2012 at 21:08 | review | Reopen votes | |||
| Nov 15, 2012 at 21:09 | |||||
| Jun 17, 2012 at 15:59 | history | closed |
finnw Community Bot |
not constructive | |
| Jun 15, 2012 at 13:11 | comment | added | Tim Abell | see also stackoverflow.com/questions/4125479/… for object vs function namespaces | |
| Jun 15, 2012 at 11:37 | comment | added | Tim Abell | see also stackoverflow.com/questions/2102591/… for performance issues | |
| May 10, 2012 at 11:44 | answer | added | Jim Jose | timeline score: 29 | |
| Apr 28, 2012 at 14:03 | answer | added | dnemoga | timeline score: 15 | |
| Apr 22, 2012 at 15:44 | answer | added | Ciarán Bruen | timeline score: 54 | |
| Aug 9, 2011 at 13:54 | history | edited | Karim |
edited tags
|
|
| May 20, 2011 at 20:07 | answer | added | Brett Ryan | timeline score: 97 | |
| May 10, 2011 at 8:28 | answer | added | Jaco Pretorius | timeline score: 1082 | |
| Apr 13, 2011 at 14:36 | answer | added | Samuel Danielson | timeline score: 1 | |
| Feb 6, 2011 at 10:42 | answer | added | Stijn de Witt | timeline score: 1 | |
| Nov 9, 2010 at 4:27 | answer | added | Fentex | timeline score: 59 | |
| Oct 15, 2010 at 2:30 | vote | accept | Scott McKenzie | ||
| Aug 27, 2010 at 23:15 | answer | added | Rudy Lattae | timeline score: 32 | |
| Jul 18, 2010 at 7:19 | history | edited | Justin Johnson | CC BY-SA 2.5 |
added 4 characters in body; edited tags
|
| Jul 4, 2010 at 4:33 | comment | added | user166390 | Take a top-level "namespace" (window property). Own it. Conflicts should be detected early on in testing. Don't bother adding all these "what if" checks. It's a fatal issue for duplicate "namespaces" and should be treated as such. You can follow an approach like jQuery to allow inhabiting a custom "namespace"; but this is still a design-time issue. | |
| Jul 4, 2010 at 4:25 | answer | added | The Who | timeline score: 9 | |
| May 26, 2010 at 11:34 | answer | added | Alex Pacurar | timeline score: 162 | |
| Mar 27, 2010 at 6:38 | answer | added | mckoss | timeline score: 8 | |
| May 26, 2009 at 1:56 | vote | accept | Scott McKenzie | ||
| Oct 15, 2010 at 2:30 | |||||
| May 19, 2009 at 8:54 | comment | added | annakata | I can see where you're going with the checking to see if the namespace is taken, but since the object will not be created if this fails I think the better approach is to alert if the namespace is taken. Frankly this should just not happen in most JS situations and should be caught quickly in development. | |
| May 19, 2009 at 8:39 | answer | added | Ionuț G. Stan | timeline score: 357 | |
| May 19, 2009 at 8:26 | answer | added | AnthonyWJones | timeline score: 33 | |
| May 19, 2009 at 8:22 | answer | added | dfa | timeline score: 815 | |
| May 19, 2009 at 8:11 | history | asked | Scott McKenzie | CC BY-SA 2.5 |