#739 closed defect (fixed)
Consider making package method detection aware of comments
Reported by: | James Burke | Owned by: | James Burke |
---|---|---|---|
Priority: | high | Milestone: | 1.0 |
Component: | Loader | Version: | 0.2 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
Dojo looks for certain methods in the source files related to package loading, both as part of the build process and as part of package loading (for xdomain and for debugAtAllCosts). However, it does a simple regexp that does not take into account that the matches may be inside commented out code.
Change History (7)
comment:1 Changed 14 years ago by
Component: | Core → PackageSystem |
---|---|
Owner: | changed from anonymous to alex |
comment:2 Changed 14 years ago by
Owner: | changed from alex to James Burke |
---|
comment:3 Changed 14 years ago by
Milestone: | 0.4 → 0.5 |
---|
Pushing to 0.5. I am not comfortable doing it for 0.4.1, since it could touch a few files. And maybe we can pick it up as part of other improvements in the build process.
comment:4 Changed 13 years ago by
Milestone: | 0.9 → 1.0 |
---|
Wanted to get this for 0.9, but ran out of time. Behavior is the same as in 0.4, but still not very desirable.
comment:5 Changed 13 years ago by
Looks like this is fixed now with the new debugAtAllCosts support that uses the xdomain loader. loader_xd.js has code now to remove comments before looking for dependencies, and buildUtil.js has the removeComments() function that is used during build.
Last remaining place is in buildUtilXd.makeXdContents(). Need to have it reuse the function in buildUtil.js.
comment:6 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Stealing io and package bugs from Alex. Holler if you want it back.