list of features removed in 1.7

[Rawld Gill]

A few features have been removed in 1.7 because they were one or more of

• no longer relevant
• never used/finished
• replaced consequent to new 1.7 features

This ticket lists such features.

[Rawld Gill]

debugAtAllCosts

debugAtAllCosts has been removed from the loader. It was error prone, expensive, and didn't cause the exact same code path. This decision was discussed and public comment was sought.

If you absolutely can not live without this feature, then do a build (make sure optimize=0 and layerOptimize=0). The output is a set of AMD modules that can be loaded asynchronously with script injection by setting the loader to asynchronous mode.

debugAtAllCosts is also used to prevent catching an exception in some modules e.g., dojo/_base/xhr. This functionality has not been removed.

[bill]

FWIW all these issues need to go into the release notes. (Not sure what the point of also having a ticket is.) Anyway, I've already added debugAtAllCosts to the release notes, see ​http://docs.dojocampus.org/releasenotes/1.7#loader-builder-related, feel free to update the description.

[Rawld Gill]

Replying to bill:

FWIW all these issues need to go into the release notes.

Do we talk about changes in private functions in release notes? For example, the fact that dojo._getText is now in dojo/_base/xhr; the fact that dojo/_base does not exist; etc.

(Not sure what the point of also having a ticket is.)

Seems to me that release notes

• are not formerly tied to the code base like a ticket
• may skip private/internal deletions
• may have less detail and not refer to other tickets / changesets etc.

Anyhow...that was my thinking

[bill]

We do mention private functions in the release notes if the changes might affect users. For example:

dojo._getBorderBox() has been removed, use dojo.position() instead

I doubt anyone will notice that dojo._getText() moved but you could add it just in case if you wanted.

[Rawld Gill]

bill was right; this was a stupid ticket.