What you probably want is to leave javascript_include_tag unmodified, even if you are freely able to monkey patch it yourself, and instead serve the JavaScript dynamically.
What you probably want is to leave javascript_include_tag unmodified, even if you are freely able to monkey patch it yourself, and instead serve the JavaScript dynamically. There are a number of ways to go about doing this, but you can make a .erb. Js file to respond to an arbitrary action.
Sorry, I'm still confused. How can you use js. Erb to find all included javascript libraries?
– Tony Stark Nov 21 at 20:31 There's no way to know this information because calls can be made to javascript_include_tag at any time with any arguments, so you'd have to exercise every page under every conceivable arrangement of parameters in order to trigger them all, something that's impractical by definition. Instead of a retrospective approach, you need one that's more declarative. Try creating your own system for defining where JavaScript files are included, like a config file or small DSL, and feed parameters in to javascript_include_tag instead of waiting for it to be called.
– tadman Nov 22 at 16:12.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.