Skip to main content

Bug Tracker

Side navigation

#14687 closed feature (fixed)

Opened January 10, 2014 05:29PM UTC

Closed March 13, 2014 03:24AM UTC

note on AMD best practices

Reported by: Owned by:
Priority: low Milestone: 1.11.1/2.1.1
Component: core Version:
Keywords: docs Cc:
Blocked by: Blocking:

Not surprisingly, jQuery has become the go-to example for developers looking to add an AMD definition to their library. As we know, jQuery's near ubiquity means that certain AMD recommendations are not practical for jQuery. Unfortunately, the jQuery named module registration is referenced with the (reasonable) assumption that it's representative of AMD best practices. I'm hoping an extra comment will make it clear that jQuery is a special case.

See for the patch and links to related discussions.

Attachments (0)
Change History (4)

Changed January 12, 2014 08:49PM UTC by markelog comment:1

keywords: → docs
priority: undecidedlow
status: newopen
type: bugfeature

Changed January 23, 2014 04:54PM UTC by timmywil comment:2

component: unfiledcore

Changed March 04, 2014 02:29PM UTC by dmethvin comment:3

milestone: None1.11.1/2.1.1

Changed March 13, 2014 03:24AM UTC by S. Andrew Sheppard comment:4

resolution: → fixed
status: openclosed

AMD: Note on AMD best practices

Fixes #14687

Closes gh-1478

Changeset: 2585ee58809c22a3c97f87b1b4aa68dbd41f386c