I suspect it could be a combination of factors. This is something that
could explain what you see:
1. Parser::Typography::Base is autoloaded
2. Parser::Typography::CharTypographer is autoloaded
3. Files change and a new request comes
4. Parser::Base is autoloaded
5.
Here's a change in behavior I would love on the mailers.
## Backstory
When you send an email, you'll likely need links. Those links must be the
full path i.e. 'http://example.com/foo' instead of relative (just '/foo').
Unfortunately most devs are so used to using the *_path helpers, they use
Totally in support of this as well. I've probably made this mistake more often
than I've done it correctly, and it's so easy to miss.
I've seen email templates go months without this being caught.
I'd probably prefer the exception route myself, just by undefining the methods
for ActionMailer.
I have been bitten by this too, and agree with it.
I think resolving a full URL would be better. People sometimes reuse
normal views from Mailers, and would be better off using *_path
helpers there.
Exceptions would cause an issue. (A warning maybe?)
Vipul A.M.
+91-8149-204995
On Thu, Jun 12,
This mailing list is specific to the development and design of Rails.
ObjectSpace is a library in Ruby itself and has nothing in particular to do
with Rails. Consider posting to one of the Ruby mailing lists instead:
https://www.ruby-lang.org/en/community/mailing-lists/
On Thu, Jun 12, 2014 at
Agree with the feature request. I made this error too.
2014-06-12 18:04 GMT+00:00 Vipul A M vipulnsw...@gmail.com:
I have been bitten by this too, and agree with it.
I think resolving a full URL would be better. People sometimes reuse
normal views from Mailers, and would be better off using
I'm in support of this as well.
As a solution i would prefer to resolve the full URL by default. Raising an
exception seems to me a bit like rails telling the programmer I know what
you're intending, and we both know the solution but you have to fix it on your
own.
Here's a change in
On Thu, Jun 12, 2014 at 8:07 PM, Florian Thomas f...@florianthomas.net
wrote:
I’m in support of this as well.
As a solution i would prefer to resolve the full URL by default. Raising
an exception seems to me a bit like rails telling the programmer „I know
what you’re intending, and we both
Is there any compelling argument for why the current structure is broken?
Is this just a aesthetic and/or stylistic proposal?
Most of the larger apps I work on have 10-15 files in initializers. Squashing
them into on 1 file not a good option to me.
Inside the app/ folder of larger Rails
On Jun 11, 2014, at 9:34 PM, Pier-Olivier Thibault poth...@gmail.com wrote:
You are right. However, the initializers is not really what's discussed here.
it's the whole directory structure. Anyway, I think config/ folder still has
its place( and the initializers for all I care). I think the
10 matches
Mail list logo
