Ticket #14687 (closed feature: fixed)
note on AMD best practices
Reported by: | andrew@… | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | 1.11.1/2.1.1 |
Component: | core | Version: | |
Keywords: | docs | Cc: | |
Blocking: | Blocked by: |
Description
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 https://github.com/jquery/jquery/pull/1478 for the patch and links to related discussions.
Change History
comment:1 Changed 11 months ago by markelog
- Keywords docs added
- Priority changed from undecided to low
- Status changed from new to open
- Type changed from bug to feature
comment:4 Changed 9 months ago by S. Andrew Sheppard
- Status changed from open to closed
- Resolution set to fixed
AMD: Note on AMD best practices
Fixes #14687 Closes gh-1478
Changeset: 2585ee58809c22a3c97f87b1b4aa68dbd41f386c