Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#16236 closed defect (fixed)

I get twice templateString cache in layer when use build system build application

Reported by: gm731958576 Owned by: Rawld Gill
Priority: undecided Milestone: 1.9
Component: BuildSystem Version: 1.8.0
Keywords: Cc:
Blocked By: Blocking:


I have a problem when build my application use 'dojo build system' in dojo-release-1.8.1-src. I download '' and '' uncompress in same directroy(D:/htdocs/dojo/dojo1.8.1/), then execute 'build --profile standard --release' and 'build --profile d:/htdocs/dojo/dojo1.8.1/demos/themePreviewer/demo.profile.js --release' in ~/util/buildscripts directroy. I get two same templateSting(import by dojo/text plugin) cache when open the src.uncompressed.js in 'D:/htdocs/dojo/dojo1.8.1/release/dojo/demos/themePreviewer/',for example has two 'url:dijit/form/templates/TextBox.html' in 'require({cache:{}})',but it is only one in dijit/dijit-all.js.uncompressed.js .I get same problem in dojo1.8.0 .

I read '' and create a profile(this file can be get from '') named my.profile.js in 'D:/htdocs/dojo/dojo1.8.1/'. Run 'src\util\buildScripts\build.bat --profile my.profile.js', the result is worse.

I wang to create some application in ~/demos directroy,then build and deploy them minimized.

What should I do?


Change History (5)

comment:1 Changed 6 years ago by iCanDo

The same error here, get dijit/templates/ProgressBar.html twice.

require({cache:{"url:dijit/templates/ProgressBar.html":'<div ...', ...});

comment:2 Changed 6 years ago by grijsje

Having the same problem with a custom layer which includes widgets using templates running dojo 1.7.0. What should be the proper fix here? No longer return the template dependencies from computeLayerContents? Or rather include the widget without a cache entry?

comment:3 Changed 6 years ago by Rawld Gill

Milestone: tbd1.9
Status: newassigned

comment:4 Changed 6 years ago by Rawld Gill

Resolution: fixed
Status: assignedclosed

In [31251]:

[31250] was committed with the wrong comment; it should have been: improved algorithm for constructing layers to avoid multiple copies of text resources in some cases; updated a demo profile to current best practice; fixes #16236; !strict

comment:5 Changed 6 years ago by Rawld Gill

Hi gm731958576,

That was a tricky one; thanks for giving me a good reproducible test case.

Note that the profile was fine (just old) and not causing the problem...I just updated it while I was working with it.

Note: See TracTickets for help on using tickets.