an
> passing it along to Rails.
>
> On Thu, Aug 29, 2019 at 11:13 AM Emile Bosch wrote:
>>
>> Thanks for your participation!
>> Hmm, maybe. However I am afraid this might get a bit cumbersome when writing
>> more then 4 fields. The word required in this sample is
&
Thanks for your participation!
Hmm, maybe. However I am afraid this might get a bit cumbersome when writing
more then 4 fields. The word required in this sample is
the longest word of this command. Maybe req? Are there any other generators
out there that tackle this problem?
Also an *
Hi there,
Like numerous times I am generating models, I go in to make fields required
and validates_presence_of them.
Would it be easy if we could just say:
~~
rails g model contact *name *email:string *age:int
~~
Simple but super easy to add and makes it all a bit more dry.
Let me know what
of additional things such as erasing
a persons data, auto expiration or requesting a dump of the data. But this
is probably out of scope.
Let me know what you think!
On Saturday, February 9, 2019 at 5:32:41 PM UTC+1, Jeremy Daer wrote:
>
> That would be wonderful, Emile! Guidance like this would b
feedback,
Emile
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to r
I’ve been building apps/apis /w graphql and webpack for some time now. I
usually start with a `rails new` then start removing all the files/frameworks i
don’t need for decreasing the cognitive load.
Over time when i need it i start adding things like mailer/sprockets/maybe
active job (if that
t;
>> link_to("Hello", root_path, class: {class: {btn:true, selected:
>> selected?}}
>>
>> I think this would be awesome, anything reasons why we shouldn't
>> implement this?
>>
>> Cheers,
>>
>> - Emile
>>
>> --
>> You
he value
>> is true)
>>
>> link_to("Homepage", root_path, class: {selected: selected?})
>>
>> -> a href class="selected" and other
>>
>> You can do the same thing to add multiple classes too
>>
>> link_to("Hello", r
ath, class: {selected: selected?})
-> a href class="selected" and other
You can do the same thing to add multiple classes too
link_to("Hello", root_path, class: {class: {btn:true, selected: selected?}}
I think this would be awesome, anything reasons why we shouldn't i
Well this is old, but still relevant :) I've seen the replies, but i've we
do it the way we wanted and just because all the other attributes are doing
it that way, i think you're doing it wrong. Rails is meant to please the
developer, making painful constructs just to make a link selected or
The problem lies in that if you aren't connected as a specified user, you
can't use the databases built in features to secure the tenants data like
Row Level Security. Or even secure the schema per customer. Simply because
the database, postgres in this case, doesn't know who you are and
i did. the issue at hand is that its hard to mitigate a sql jnjection attack
without setting users at connection level.
this wouldnt mitigate it.
Sent from my iPhone
> On 12 Dec 2015, at 22:01, James Coleman wrote:
>
> I don't currently have easy access to a PG 9.5 box, but
this desired behavior.
I hope i made myself clear a bit,
- Emile
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rubyonrails-cor
Since FK's are now accepted and in rails 4 how about we fix polymorphic
which something like this?
https://github.com/wegowise/polymorpheus
Anyone from core ideas on this?
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group.
To unsubscribe
from me.
Emile
Le 2012-06-21 à 09:48, daniel2d2art a écrit :
Hi guys, I'want to introduce this discussion (I'm looking for similar here,
but don't found it)
Actually the scopes chainity is glued with AND operator.
Some times we need to chain the same scope implemented method using both
15 matches
Mail list logo