Opened 10 years ago
Closed 10 years ago
#14687 closed feature (fixed)
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: |
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 (4)
comment:1 Changed 10 years ago by
| Keywords: | docs added |
|---|---|
| Priority: | undecided → low |
| Status: | new → open |
| Type: | bug → feature |
comment:2 Changed 10 years ago by
| Component: | unfiled → core |
|---|
comment:3 Changed 10 years ago by
| Milestone: | None → 1.11.1/2.1.1 |
|---|
comment:4 Changed 10 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | open → closed |
Note: See
TracTickets for help on using
tickets.
AMD: Note on AMD best practices
Fixes #14687 Closes gh-1478