Namespace mappings do not apply to files included in a static resource bundle

[Phil W]

We have client-side code (JavaScript) that has hard-coded usages of our managed package's namespace. These references are not replaced as part of the deployment which breaks our client code.

I understand that, at a technical level, the namespace mapping is applied after the bundles are generated, just prior to deployment, and that any binary files (including these ZIPs) are not processed. Clearly we really need this to apply just before the bundles are generated (or just after they are exploded on the retrieval side of things).

This is quite a serious issue for us (meaning that our current releases have pages that do not work at all).

[Scott Wells]

FYI, this is implemented now. I want to run it through some more extensive testing before releasing it. My guess is that I'll post a build with it Tuesday or Wednesday morning. I'm happy to post a pre-release build here tomorrow morning if you and your team want to give it a whirl as well.

[Phil W]

Hi Scott, happy to try a pre-release (though of course we are some time zone differences so we may not get much time before you are ready for a full release).

[Scott Wells]

Phil, I'm going to use it all day today to make sure the refactorings required to namespace substitution and substitution rules are solid. All my testing yesterday looked good, but before I unleash things on the mass hordes I like to subject myself to it heavily a bit first. If it holds up well today, minimally I'll post a pre-release build here this evening, and likely I'll just release it tomorrow morning.

[Phil W]

Cool. Sounds good to me. :)

[Scott Wells]

Delivered in 1.8.3.3 and 2.0.2.6. Both namespace translation and substitution rules should be applied to static resource bundle files when the bundle is archived as a static resource for deployment and when an archive-type static resource file is extracted for retrieval. Please let me know if you find any issues.