Page MenuHomePhabricator

Allow CelerityResourceResponse to hold resources from multiple maps
ClosedPublic

Authored by epriestley on Jan 1 2014, 4:37 PM.
Tags
None
Referenced Files
F13181161: D7876.diff
Thu, May 9, 9:17 AM
Unknown Object (File)
Thu, May 2, 10:51 PM
Unknown Object (File)
Mon, Apr 29, 1:41 PM
Unknown Object (File)
Wed, Apr 24, 9:48 PM
Unknown Object (File)
Sun, Apr 21, 3:47 PM
Unknown Object (File)
Wed, Apr 17, 2:43 PM
Unknown Object (File)
Apr 11 2024, 7:13 AM
Unknown Object (File)
Apr 9 2024, 5:28 AM
Subscribers

Details

Summary

Ref T4222. Currently, CelerityResourceResponse holds response resources in flat maps. Instead, specify which map resources appear in.

Also, provide requireResource() and initBehavior() APIs on the Controller and View base classes. These provide a cleaner abstraction over require_celerity_resource() and Javelin::initBehavior(), but are otherwise the same. Move a few callsites over.

Test Plan
  • Reloaded pages.
  • Browsed around Differential.

Diff Detail

Branch
celerity9
Lint
Lint Passed
Unit
Tests Passed

Event Timeline

I can help with the require_celerity_resource => requireResource() and Javelin::initBehavior() => initBehavior() if you like.

I don't think it's hugely important, I mostly wanted to just put enough of them in to make sure it works. But feel free to run with it if you're feeling like grinding some stuff out. The only gotcha is to make sure the callsite is in a View or Controller before converting it, but 95% of them should be (some cases like Remarkup rules or Phame templates might not be).