00:00:07.480
in this uh how to say like scenery like such a it's a very Co weather we just
00:00:13.880
need like a fireplace with like maybe we had like a new monitor we just having a a fireplace on the side making it even
00:00:20.160
more cozy especially with the bitas the traditional food to eat in this cozy weather so yeah so my name is R uh you
00:00:28.599
can find me everywhere are as rust tank of everywhere I have like a substack
00:00:35.120
called tips where I share some random tips and because again there is a lot of
00:00:40.680
food here and uh always people make photos of the slides and I change slides
00:00:46.440
very fast and I show a lot of presentation so all my code from all my slides are already listed here so you
00:00:53.520
don't need to kind of frush your phones and just uh take photos there will be a lot of code because I like doing Cod
00:01:00.399
when I can so yeah today uh so if we talk about rails there is this slogan
00:01:05.880
one person framework and uh right now I'm the CTO the founder and the only engineer for
00:01:12.200
the next 12 days uh we have some new people
00:01:17.960
coming in but uh I buil this startup it's going rebuilding and basically uh
00:01:24.880
I'm one developer I build the whole system I build the mobile app for iOS Android and basically a big chunk of
00:01:32.399
that was because rail really is the one person framework like honestly again without rails I would have spent a lot
00:01:39.280
more time and coffee and unhealthy food but yeah Ruby on Rails is like a great
00:01:45.000
tool it's like an amazing thing to build and often again when we choose Technologies when we choose things uh
00:01:53.600
when you need to build stuff I'm always like asking when people want to build stuff should I do something new should I do something C and I'm like
00:02:00.560
uh first again if you want to build a product use something you know in without the only exception is if the
00:02:07.719
thing you know cannot solve the particular problem of the things you want to build if there is like unique technologies that enable stuff because
00:02:14.239
one problem with the new exciting Tech is there is a lot of fail scenarios which you don't want to do like for
00:02:20.440
example should I use this other cloud service uh I don't know does it have something better I know o AWS books and
00:02:29.200
I know how to work around them that's very important so yeah so we all know rails rails has a lot of things included
00:02:36.800
in in in the Box a lot of packages a lot of packages that people actually this is like if you open GitHub this is all the
00:02:44.200
rails gems with all the stuff that come here surprisingly some of that stuff I
00:02:49.400
have never used in an actual project uh like the M the the thing which receives
00:02:55.360
emails and process them and do all the magic with them for example something very useful but but it has a lot of
00:03:00.840
things and again if we open like a new rails project we see a lot of like things being included a lot of batteries
00:03:07.440
included and that's amazing that's great usually when I come here I just like comment out some of the stuff I don't
00:03:14.000
need to change some defaults but in general rails and the EOS system has a lot of B pieces and again it helps you
00:03:21.360
build a lot of like nice apps and out of architectures but there is also one part of rails where it's still again every
00:03:29.040
project is different every project kind of has to build a lot of like its own combining the pieces but also there is
00:03:36.599
some things that are in my opinion missing that this is something which I noticed like from a from a lot of other
00:03:42.599
projects I always have those places which I just copy paste from Project to project some settings some things and
00:03:51.000
it's always a lot about like uh the funny thing is I have this photo and the
00:03:56.319
caption is R laughes active record and does this look somebody who loves that something I'm not very photog gentic
00:04:03.000
here but yeah uh in general again I really like Ruben royos is like one of the best things and because when you
00:04:08.319
love something and you become an expert with it you know all the things it's missing so today I'm going to have two
00:04:15.319
things I'm going to share like one things is rail extensions like things
00:04:21.280
which I basically copy paste from Project to project to project to project to project and some missing Concepts
00:04:28.280
like things that there are still not not in rails and it's stuff that I have seen in a lot of projects people just invent
00:04:34.639
the things around those things and one one one funny thing was
00:04:41.240
when I was making the rails extension part I'm like oh this is Ping from rails and I'm like maybe I look at the
00:04:47.520
documentation and they see actually rail had this thing so I found some features with like shallow shallow routes and
00:04:54.560
some parameters that were actually I didn't know they existed so the things I'm going to talk
00:05:00.440
today is like active record routing Arrow handling and internalization and again some of those
00:05:08.160
things are basically things I put in every project like the first thing for active record and this is honestly every
00:05:14.039
time I go to a real project even if I don't own it I add this gem it's called
00:05:19.360
annotate which basically puts this comment in front of every active record
00:05:24.479
model and it's honestly I have no idea why it's not in rails or ar doesn't have
00:05:30.039
something like that that it doesn't have it
00:05:35.919
builtin somebody doesn't like yeah I that's a personal opinion about all those stuff uh the thing about it is a
00:05:43.440
lot of the times you open a model and you have you don't know what are the fields you have to for example go to the
00:05:49.600
schema often what are the indexes what are the foring keys like a lot of the
00:05:54.680
stuff for me this gem is basically a must like yeah some people don't like it
00:06:00.039
some people yeah but I don't want to go to
00:06:06.599
like the schema because the schema is an sqo file and when the schema oh the way you can ask questions you can disturb it
00:06:14.199
because it's a lot of like discussion Parts but yeah I mean it's the thing but for example that
00:06:20.400
that's why we added it because we have schema SQL with very complex SPO queries and you always have to jump between two
00:06:26.240
three four five six FES and having this your file it was actually very useful
00:06:31.840
and also when you see it like that it's very obvious for example you notice bugs here like oh something here is not null
00:06:38.599
like why account ID and user ID in this thing is null like why building user ID
00:06:44.479
is null here what's the reason and you notice a lot of things when it's like right that another thing which raos has
00:06:51.360
it built in and it's amazing and I'm a big fan of counter caches raos has a buil-in counter cache which is great but
00:06:59.240
it's great for like when you have a very clear so what counter caches does first
00:07:06.240
is when you have a column which counts how many records of some relationship
00:07:12.120
are in the project so in in general rail terms you only count the whole
00:07:17.680
relationship but often for example let's say you have a user and oh actually here
00:07:23.800
I have an apartment apartment belongs to building and some of the apartments are archived apartment department so you
00:07:30.240
want to have a separate counter for that and this G Counter Culture what I like
00:07:35.840
about it is allows you to add a lot more complicated counter cache things so The
00:07:42.400
Counter Culture gem is basically an extension to the counter caches and it
00:07:47.639
works amazingly well especially again if you have an application that does a lot of calculations and it also uses counter
00:07:54.440
caches not only for counting columns but it can also do things like okay
00:08:00.080
do a counter cash based on the sum of all transactions so you don't need to write a lot of the code so again real
00:08:06.199
has this as a concept but this is a gy I basically add by default in every project another active record concept
00:08:14.400
which I personally copy paste from every project is this thing which is called belong to
00:08:20.240
polymorphic so raos has polymorphic associations and again they are controversial some cases you use them in
00:08:26.639
some cases you don't it's very useful when you need to attach things to other things like let's say you have comments
00:08:32.440
and you want to allow a lot of Records on your system to be commentable or in
00:08:38.039
my case I have a note and the note can be attached to many things one problem with the default rail implementation is
00:08:43.760
if you just say belongs to polymorphic true you actually don't have any information about what are all the
00:08:50.360
possible types that I can actually have this polation being part of it's a lot
00:08:57.320
of like chasing uh uh what is this and yeah you can do go in the production database and
00:09:03.519
list all the changes because most probably locally you won't have everything but having like just
00:09:09.480
basically belongs what it does is basically validates that those are all the classes that have nodes to and I
00:09:16.760
have found that in like bigger projects when you don't exactly know what happens
00:09:22.320
it's very it's a lot easier to know oh this is what this things can have also
00:09:28.760
there is a con in rails which it's called delegated types how many of you have used delegated
00:09:34.839
types yeah it's it's kind of similar the problem the thing with delegated types
00:09:40.040
it's the reverse Association like delegated type basically tells you my type is this and I delegate to this
00:09:46.040
while polymorphic is I own this so delegated types actually have the same
00:09:51.440
concept like over oops sorry
00:09:57.640
yeah five tickets yes yeah so uh delegated types I was very surprised but
00:10:04.560
also delegated types actually had this things so it's not something I can imagine being in real some days that we
00:10:10.440
say oh this polymorph Association allows you only these types um and again another thing which I do in
00:10:19.600
my projects which is I have never seen somewhere else so we know how in rails
00:10:25.600
we have the concerns when it's like include concern and concerns are
00:10:31.320
trade if you don't overuse them uh but I found I found them a bit limiting
00:10:37.600
because imagine you have a concern like uh has audit log for example imagine
00:10:45.079
this is a concern and I say this issues activity has an audit and I want to get
00:10:51.160
all the fields except this one so having it with a regular concern you need to
00:10:57.440
define the static method in the concern then you have to keep that state you need to call this method you have to
00:11:03.079
remember to call this method for example I have this extension it's
00:11:08.440
called angry support time as Boolean like for example I have a extension which like this field indicates that I
00:11:15.279
have a Boolean field which takes its value from like a time at coln and if I
00:11:21.200
have to do this with concerns I need to do a lot of like meta programming a lot of like need to Define like a static
00:11:27.000
method then I have to include the concern they need to do and concerns work amazingly well when you need don't
00:11:32.720
need to configure them like like let's say this modification subject is very in easy thing I can do I can say include
00:11:39.839
notification subject and that works out of the box all settings and all of that so again this is very kind of like
00:11:47.880
concerns uh but what I do with my um with my extensions the way I do them
00:11:54.920
from basically every record is my extensions just just have one method
00:12:00.040
which is called defined and it receives a model it receives its settings and it does all the magic that's kind of needed
00:12:06.000
for its record so it's done basically it decorates the record it also works as uh
00:12:14.880
if you noticed it also works this I here is not so visible but also what we have
00:12:21.480
some extensions which are basically concerns yeah yeah basically everything we I don't use in my project I don't use
00:12:27.519
concerns I just use those extensions because EXT I will show you the call of
00:12:32.839
the extension but this basically allows me to say okay this is the model this is the field and this is basically what they need to do for like BR field like
00:12:40.199
there is a lot of code here imagine doing this with like concern you have to do a lot of this orchestration yourself
00:12:46.160
and the user who the user who uses your concern has to call those methods by themselves they have to know what are
00:12:52.240
the methods what the conventions and they have to do a lot of work and you need to add a lot of methods to the
00:12:59.760
whole model and the implementation here is very simple you just say extension
00:13:05.600
the extension module just call def def if there is if there is not you just
00:13:11.120
basically use it as a concern so every concern actually go can be also an extension so this is a small trick I
00:13:17.440
kind of use in all my projects and it helped me a lot with exactly those concerns which are more like oh this is
00:13:23.399
like a small Library here like like for example have an audit loog and just say okay don't I I care about all the fields
00:13:29.720
except those ones so this is something I haven't seen anywhere else done so most probably I'm
00:13:36.440
totally wrong when doing it but it work quite well in like five six places where
00:13:41.959
I introduce those things uh routing so rails routing I really like
00:13:48.600
the rails routing in general it's great also rails has this concept which
00:13:53.720
honestly JavaScript World Is Still discovering it you actually can have methods that you call and generate the
00:13:59.959
route and the methods and the routes are different so you actually can have a nice routing methods and a nice URLs and
00:14:07.279
you don't need to remember routes but with routes there is one thing which is always missing I want to use my route
00:14:13.600
helpers outside of the mailer and the action pack this is something in every project I need some way to get the
00:14:20.720
routes for example I want to do a push notification I want to send an SMS I want to do uh I don't know just use the
00:14:28.519
routing outside of my main life cycle of the method and rails actually has that
00:14:34.519
you can do rails routes and do it and then it blows up because you don't have the default URL options because it
00:14:41.800
doesn't know the domain it doesn't know a lot of that so in every project I I basically have this class it's called
00:14:48.120
routes I include these rail URL helpers I set the default options and everything
00:14:54.399
works I would focus on this routes customing a bit so sometimes there is in
00:14:59.480
rails there is this awesome method it's called URL 4 which it gets a method and
00:15:04.560
like a class and it and it gets its route but the problem is if your routes
00:15:09.600
are named differently than the models if you have Nam spacings if you have like that so also one thing with rails routes
00:15:18.320
is sometimes I actually need custom routes like imagine you have like a route which accepts a build like in my
00:15:25.240
case I have an account accounts have buildings and I can filter things by that so I want to say I give you a
00:15:31.120
building and you give me like the transactions of this building and it it takes the account of the building for
00:15:38.440
making the route I want to have like a custom route method and in raos having a custom route method where do you add it
00:15:45.399
how where does it get into the system so what I do is I have this routes custom I default all the routes there they're
00:15:51.839
included in all the places where the routing is included and also in this rout helper so in this way there is no
00:15:58.120
difference between my custom routes and rails routes and for example instead of URL
00:16:04.079
full I have something which I call the record pth and I do things like that there which not that pretty but it's
00:16:09.839
very useful in my system because I have a very clear mapping between oh this is my CRA this is my models this is my
00:16:17.560
methods and it down fors to R for it it I found this very useful because it
00:16:23.639
clean up a lot of my routing places because if you notice some of my routes are very long and also having this P
00:16:33.279
record and using the URL for in general cleans up a lot of like you can make a
00:16:38.519
lot of generic helpers instead of just passing those strings so this is another technique I
00:16:44.560
have found in a lot of places so another place in rails which
00:16:50.560
rails has a lot of building tools and it's very great it's Error infrastructure and why it's Error
00:16:57.120
infrastructure is great is because a lot of gems can actually plug in into rails and get all this data and do a lot of
00:17:03.880
that parts for you like you can put something like Sentry you install it with two clicks or New Relic or whatever
00:17:11.679
and you get all the error back however I have found that in all the project I make a custom module all named error
00:17:18.480
reporting because every error reporting framework is it Sentry is it hub spot is
00:17:25.480
it signal whatever needs things like okay I need to assign a user like to say
00:17:30.919
in my controller where my user logs in this is the user who this error is for
00:17:36.520
because often when you see an errow you want to know who the user is you need to get this data also I have used couple of
00:17:44.280
other helpers here like uh capture exception and exception uh context like
00:17:50.280
for example often I need to be able to capture an exception in my error tracking and for the user they don't
00:17:56.799
need to see that exception like sometimes when I write code and I get some error State I use this kind of like
00:18:03.039
a more advanced lock so having this as like a facade around the service like
00:18:09.799
for example if I want to use something else in the future I can just change it also there is some useful things like
00:18:15.799
for example with active job uh if a job is
00:18:21.559
discarded uh like for example it was to Tred too many time you call discarded via some helper or something around it
00:18:29.000
there isn't like in rails as far as I know none of the exception trackers by default track all the discarded jobs
00:18:35.080
where did they come from there is a thing there but you need to like tune it very slow so I also have this explicitly
00:18:41.720
called in my Base active job if the job is discounted please tell me about it also again there is a lot I can talk
00:18:49.200
about exception some self-promotion I have this talk with videos about it's
00:18:54.280
called living without exceptions it's a lot more Deep dive on how to have
00:19:00.039
exceptions so internalization having like internalization tools in rails they're
00:19:07.039
actually amazing like I'm very happy about them the they are a lot into the
00:19:12.280
whole core of the system you can basically have a lot also internalization in Ruby in general and
00:19:19.880
this is very unique to Ruby because I have tried to do internation in other languages Ruby has this magic thing
00:19:27.760
called a symbol which is different than a string and there is and in other
00:19:32.840
Frameworks they only have strings like JavaScript and all the things so with Ruby what we can do in a lot of places
00:19:38.960
is if you pass a symbol the symbol can be treated in a different way so for example I have this helpers which I
00:19:46.000
inject directly into my E e88 help one is called T display and T
00:19:52.520
display is basically a think which accepts another thing and give you translations of it so if I get a symbol
00:20:01.159
and that's the magic of Ruby that's honestly not not other Technologies can do something that clean if I give you a
00:20:06.840
symbol just translate it just go to the translation table translate me my string
00:20:12.360
works perfect if it's a string okay just display it so if if this is the username
00:20:17.640
if I give you a string just translate it uh apart from that I have my own tool
00:20:24.320
link around uh to display if this is like a record if it has a display name just use
00:20:30.600
a translated display if it's a name name title ra has some ways to do like
00:20:36.840
default naming of Records but they don't have one which is explicitly used for
00:20:43.000
translations but this is something I have found when you do translations in a project having AER like this cleans up a
00:20:50.360
lot of noise uh and a lot of the times you actually want to say oh I I I know what the text needs to be and sometimes
00:20:56.880
you want to do the key and this this part is particularly R magic because none any other technology has like
00:21:02.679
symbols like again some El here like but for example JavaScript sft and other
00:21:08.320
things don't don't have that another two helpers which I find very useful my is
00:21:13.720
two options which is basically you give it a collection of records and it just returns them to display them so
00:21:19.960
basically I can say oh here is records give me all their translations in a list
00:21:25.360
and how they are displayed and I have t which re receives an in from like
00:21:30.720
imagine you have a drop down when you pick the status of a product or state you just okay here's my keys and I just
00:21:38.000
guess the key name based on that internalization and also this clean up a lot of the
00:21:43.919
stuff another thing this is more particular for my project I have those two helper methods which I created one
00:21:51.080
goes to all the translations and matches all the files if there is missing strings in them like if I have a
00:21:58.000
transation in Bulgarian but I don't have it in English this will blow up and this goes to open Ai and just fills up the
00:22:04.360
missing Keys which works surprisingly well like I was able like I didn't know
00:22:10.919
Spanish I needed to translate like 3,000 keys in Spanish and then I give it to
00:22:16.880
somebody who understands my domain and understands Spanish and he only changed like three words and the only reason he
00:22:22.960
changed him is like yeah that's correct but in this domain this is a bit more specific and actually this word quite
00:22:29.039
well like just when you have like translations in your project just go W them through okay my CI ures I don't
00:22:36.039
have missing keys and if I have missing Keys okay just go to something that translates
00:22:43.159
them all right yeah this is some some tips around internalization if you care
00:22:48.640
about it like uh because I did a lot of work with internalization the last few years always raise erals in development
00:22:55.720
Only log them in production uh don't I I don't like using the nested keys with
00:23:02.840
rails like in your translations you know you can have like nested Keys you can just C them by name which work well when
00:23:09.440
you have like a framework like rails that can Nest errors but I have found that it's a lot more simpler for me just
00:23:16.960
to have those symbol underscore divided places it's easier to parse the found
00:23:23.200
sort it find the missing keys and honestly most of the time when we use that do use dot here or use underscore
00:23:30.559
it doesn't matter that much but it makes it a lot faster to work with also again
00:23:36.080
use defaults like a lot of the times which I do in my project is oh I have a table column like I have my tables and I
00:23:43.440
say the table column name is this but if the table column does it's not translated maybe it's a form label
00:23:49.120
because most probably it was entered by a form so I use a lot of those
00:23:54.480
defaults so that was like some of the extension part of the Rails any questions
00:24:00.640
comments Kate from Gennady show youor oh that would be fun is it 20
00:24:07.919
Lines no no no all right so some of the missing
00:24:15.120
concept so this is things that we basically have in every project so we
00:24:20.880
need to have some UI view things we need to deal with external Services we need
00:24:26.640
to have some kind of like public and things that are permissions we need to do the service
00:24:32.600
object form CER object so the view components like this is something missing in rails it almost got into
00:24:40.200
rails but long time ago remember remember the talk from balcon Ruby about
00:24:47.760
it yeah but view component basically is a tool coming from GitHub which is like you can basically use classes to Define
00:24:55.000
your um your helper like basically Define your UI instead of using helpers
00:25:01.720
because with helpers there is a lot of mess around them and with partials there is even more mess even with the new
00:25:08.159
thing with the partials when the partial actually know yeah the strict Locos of the paral is amazing but they still have
00:25:15.039
those problems and having view components allows you to just Define
00:25:20.480
classes very simple classes and also they have this awesome plug-in which is the the main the other reason to have
00:25:29.360
this is the the same way in rail mailers have the mail previews which are very
00:25:34.399
easy to do there is these view view components previews that you can
00:25:39.679
basically have something like this and again having all your view components
00:25:45.440
being able to be separated and developed in Works quite well and do you use view component do you use flex components or
00:25:52.440
anything else doesn't matter in my opinion the question is it's really nice to have a class with some local logic
00:25:59.919
with private methods to do some complicated things and be able to be kind of
00:26:05.600
testable in separation I like and I can talk a lot about them and I have talked a lot about them here is a talk from I
00:26:12.520
think Ruby bannet a couple of years ago about view components and I also have like a whole
00:26:18.600
post about it so let's go to another thing external services this is
00:26:24.000
something we all hate and we all need to doal about it and the other thing is I have to it every mature El project uses
00:26:30.760
every popular and not other popular networking gem this is something which is like why we have two 100 networking
00:26:37.520
gems and I know why everybody like dislikes something about them and it's
00:26:43.000
like all right we have them and there is so much about them and in my opinion
00:26:49.880
this something again rails like before active jobs was in rails we had a lot of
00:26:56.559
like job related things things we didn't have a common interface and I'm surprised rails haven't done anything
00:27:02.640
with like oh there is active networking or something like that
00:27:09.640
where yeah I I mean think about it 2002 building part of rails which you can
00:27:15.080
actually depend also when we deal with networks this is something this trick
00:27:21.159
actually genady taught me long long long time ago in a galaxy far far away in
00:27:26.720
Germany we had is I have this module when handling errors which in so I have
00:27:34.640
this module called handle network errors and I don't know if you know when in Ruby you do uh TR catch blocks uh if you
00:27:44.399
pass this module as the Handler it's going to call the triple equals method of the class so that's how you can
00:27:50.200
actually match if an error matches the the error thing so I have this handle network errors and I basically have
00:27:56.760
listed all the exceptions of all the libraries that are included in my project so basically I have like 200
00:28:04.159
error here because they're all kind of the same in a lot of the times you can again split some some of the time out
00:28:09.960
some of the 500 but you just put this here and you can have like a single way to handle all the errors this is
00:28:15.919
something I do right now in a lot of my projects I also a lot of times I actually use this with active job where
00:28:22.919
in all my active jobs if there is like a network error do like five retries
00:28:28.200
otherwise discard the job lock it and so on and so forth one great thing with rails which
00:28:35.679
I'm so happy they added this a long time ago is the secure credentials in the yo
00:28:42.760
file so this is amazingly having this because before that we need to juggle
00:28:47.840
environment variables or we needed to do a lot of like the key security like K KS
00:28:55.120
and other Amazon sounding weird things so this is always great I always like
00:29:00.679
for example when I do Services I always have that keys in my system I have the
00:29:07.600
service name the token the secret and I always have this comment by the way please every time you add something to
00:29:13.000
this file if you learn anything from this stock at this comment this key is taken from this URL I especially if it's
00:29:20.679
a Google service with Google services you have no idea where this k key comes from and every time I have a poqu W and
00:29:28.360
I see this file ex change I go in and I beat people with a head if they haven't had this where do you get this key from
00:29:35.720
because I cannot tell you how many times some developer on the team registered with their company account to some
00:29:42.799
service and they didn't use the company account of the service so when they leave and their service expires the keys
00:29:51.000
uh blows up and we're like where did this key come from especially now when people just randomly register for open a
00:29:57.760
keys that's a problem to have that there another thing I do to battle the
00:30:03.600
external Services stuff is everything which I do in my projects regarding
00:30:09.120
external Services is grouped into its own namespace it's always called external it's namespace so I know if I
00:30:17.840
call it that means Network external is always a network called I have this template it's always like a
00:30:25.760
documentation like okay this is the server this is the URL of the service this is where do we manage tokens from
00:30:32.080
this is the API documentation if we are using a jam this is the jam that's being crapped by this service the idea here is
00:30:39.760
if you have 200 of those Services it's very hard to know details around stuff
00:30:46.279
also I have it like my favorite extent cell so it's this is just like a facad
00:30:52.760
in front of all the external services and this facade based basically
00:30:58.639
always have documentation around okay we are calling this method from this documentation with this area and here is
00:31:04.279
an example with unsplash like unsplash is a service for images so in a project
00:31:10.559
we needed to have with unsplash two things search and tracking download
00:31:15.720
because they want you to track uh the downloads and this is how this look like
00:31:20.840
I was like okay my services and splash this is the documentation this is the gem we are
00:31:26.200
using this is the port portal where we get our o tokens and this is
00:31:31.720
documentation here again this is the wrap of the URLs here we also handle the
00:31:36.960
errors like we hide all those networking errors regarding this and for the developer they just use this and every
00:31:43.519
time you want to say oh I just need this one search place in one product in my
00:31:48.960
application uh that's a problem because you again you don't know what are the external calls your application does
00:31:55.279
another funny thing was on a project uh I helped with they didn't have that
00:32:02.000
and they needed to block all external network Calles from the fire rall of their like pots and they were like do we
00:32:09.039
call this service and they had no idea which were the upcoming networking calls and if you have something like this it's
00:32:15.039
very easy just go to one folder and just go next next next next next I actually have a blog post about it with like a
00:32:21.080
long dealing more with external services so networking again is something where
00:32:27.240
again rail has some great fundamentals but we need a lot of the times people just okay I just run this gem I'll just
00:32:33.639
include it and we use it directly and the main thing in my opinion is never
00:32:38.960
just use the gems directly just WRA them so if they change versions if they
00:32:44.279
change apis becomes very hard like something like stripe for example uh
00:32:50.440
yeah it's very big action point but it's really good if you just had all the networking which
00:32:56.559
you don't own in its own like bucket even if it's a lot more C if you think
00:33:01.799
why should I make two codes here it makes sense when you when they break API or you need to update another thing how
00:33:10.080
with time 20 minutes okay I'm done in five I'm joking I'm not
00:33:17.919
so another thing we have something uh it's policy objects like raos right now
00:33:23.840
have this awesome Tools around how how you can make your own uh logging system but what one one area
00:33:31.720
which kind of is still missing is how do we authorize how do we handle the authorization in like a rails project
00:33:38.039
every project kind of like thinks about like the authorization themselves right
00:33:43.080
now I think the most popular gem is pundit pundit pundit what that's I think
00:33:49.840
I personally use a project because pundy didn't exist like 10 15 years ago I had
00:33:56.080
a gem called Kitty policy which is my own version of like policy files and again this is something I
00:34:04.440
personally use project to project to project because kit policy is just a GMI road to build authorization system
00:34:11.440
particular for each project and kit policy is very simple if you don't use Kitty policy you just write something
00:34:17.720
like this this is how Kitt policy started we have a file which was called application policy and this is like all
00:34:23.720
the permissions our system needed to apply it used my favorite extend self method with like static methods which is
00:34:31.639
like can access account user account if the user is null return false if the user is admin or if it's account member
00:34:38.560
the user like having this file with like 200 methods this this basically is the
00:34:45.119
authorization system which I found very useful because all the authorization was in central place it was big it was
00:34:52.159
obvious it was easy to test it didn't have any state it didn't do any
00:34:57.800
so this does zero allocations uh because one thing if you have like something which I don't like
00:35:03.560
about pundit is you need to insatiate a lot of classes and you do a lot of gu work with class names with like a long
00:35:10.680
structures and if you have like a graph Q API where every field you have to
00:35:16.400
authorization check if the user can see this field or they cannot it becomes
00:35:21.560
really a lot of like oh lookups and things like that with here again you have zero can just say okay just
00:35:28.440
guess me a new method name and just call it and um what quity policy does is
00:35:33.880
basically this method here becomes something like this it removes some of the noise like it
00:35:40.240
doesn't need to check if the user is a guest it can say okay this is the policy this is the method it basically
00:35:46.320
generates the same name method here it just got like a small DSL to do that basically skipping me this part and make
00:35:54.319
it more consistent the naming so I can do do things like can a user action
00:36:01.160
whatever can out this is a Boolean operation so this returns to for all
00:36:06.280
this blows up where the user cannot access certain things so this Rises like
00:36:12.000
and this is basically what Kitty policy is on two level it's like 20 lines the
00:36:18.480
thing about it is in my current startup we have uh a very expensive permission
00:36:26.079
system with a lot of like rules a lot of business rules a lot of roles so we have
00:36:31.160
this custom Ro DSL for our particular application which was built on top of up
00:36:36.680
K policy because again with the policy system of every application is different like what you need is not like oh this
00:36:42.920
is the exact solution this is the building blocks to build your own solution for the authorization so what I
00:36:49.319
have here in my startup particularly I have something which I call it roll stacking that means that for example the
00:36:55.640
D the the D the director has whatever the director can do whatever the
00:37:01.599
supervisor can do the operator the cashier so I have like this Branch stre so I can just write this DSL which is
00:37:09.400
like building cashier can view withraw that means the supervisor the the
00:37:15.040
director the operator can also do that so I can list all the actions and everything here kind of works and I have
00:37:23.280
basically have one this oneliner to basically Define like a map of all my permission of all my systems so every
00:37:30.960
time I need to adjust those is very simple and right now this was like two weeks ago when I was making this slides
00:37:36.280
this file had like 273 lines from those lines like 20 are like just comments
00:37:41.839
dsls and things like that but there were a lot of rules and imagine those 200 if those were like classes with like 20
00:37:48.640
lines of class names with a lot of and I just want to have like this simple map
00:37:53.960
and the other thing which was very key for me is having those methods especially this one so application
00:38:00.920
policy authorized I can call it from everywhere I don't need to think about a class name I don't need to think anything so in my application I have
00:38:09.200
those things which I enforc one is called require account uh require
00:38:14.480
account feature so this checks the current account it blows up if the account doesn't canot do calendar but
00:38:20.800
the key here is find record find record is uh price to find this record and if
00:38:29.400
and it checks if the current user can actually see this record like for
00:38:37.960
example so here I can give it like a option authorized method so um I have
00:38:44.200
this system here where if the user for example cannot find a
00:38:49.880
record this blows up with Kitty policy access Denine I can actually put this in
00:38:55.760
my error reporting so I know somebody tried to access something they shouldn't most probably I have a link somewhere
00:39:02.040
which is not with the can and the user collected by mistake and I have like a system on out toiz but this is how find
00:39:08.599
record actually looks like it's a very simple method which every record to my
00:39:14.079
system goes to this thing because every most of the time when you are trying to find something you start from somewhere
00:39:21.400
so find record does like okay find me get me the scope or like figure out it
00:39:26.599
then goes to the out right like okay now can this user do whatever what with this
00:39:33.160
record and then it was I also have this check here is if I had this required
00:39:40.520
feature calendar and checking if the account of the record actually has this
00:39:45.599
feature because I can draw a about of things and having this method actually was very awesome like I started my
00:39:51.800
project this part here didn't exist like this part didn't exist with the fin record and because didn't
00:39:58.640
exist uh when I needed to add oh I need to restrict certain actions because we
00:40:04.400
now have two plans I just changed these two lines and it didn't change anything in my other controllers I also here this
00:40:11.960
method actually has five five six more things like for example if your account is deactivated you shouldn't be able to
00:40:18.440
do almost anything so I also had this logic here so this find record is very useful when you build like a system to
00:40:25.880
have like a single place where all the loading of Records come from because
00:40:32.960
it's very useful for you to kind of have have the central place to check the authorization not to think about oh I'll
00:40:38.880
think it on a controller level just think it on like a loading level uh another thing which I have
00:40:44.839
found out useful in my project in particular I have noticed a lot of people also do it is a lot of Records in
00:40:51.280
our system are trees like they have an account the account owns something else like a project the project on a task and
00:40:58.680
from like every record you can actually go to the root of the tree in some way and you care about the current user
00:41:06.520
related to the to their account level like so I also have this thing which is like accounts get me the account of the
00:41:13.160
record and in this way I can say is this feature available for this record where
00:41:18.240
I go to the tree get the account and just say Okay this feure available so yeah that's the kitty
00:41:24.680
policy gem but the idea here is not the gem itself because again it's 20 lines uh but the idea here is if you build
00:41:31.400
your authentication system you do it in such a way that it's kind of encapsulated and it happens in your whole system it's not something that the
00:41:38.079
developer should think of uh
00:41:45.200
okay and yep I need to just come back so yeah so so far so good so much
00:41:53.760
content you have no idea how much I get from this presentation so uh service objects like this is like
00:42:01.560
something where there is a lot of debates a lot of discussions and for me honestly that's my service object no
00:42:09.400
external libraries rails doesn't need to solve that it's just I do this for SE subject I just have a module I do extend
00:42:16.680
self I have like a usually method call if I need multiple methods I just have multiple methods everything else is
00:42:22.760
private I don't care like for me that's like the most simple way to start and doing stuff and then again if you need
00:42:29.400
you add like I I I have thought oh maybe I have like an application service object or something like this but there
00:42:35.800
is so much stuff you don't need here so yeah personally what I do is just I have like service objects which are just
00:42:42.480
basically functions like a globally named functions and I use the method call because I can actually use the the
00:42:49.440
Ruby building uh use of calls in different places like for example is it
00:42:55.800
uh Lambda is it like proc is it like a model with a class. a CO it's the same
00:43:01.720
so I can do a lot of my service object compos them uh the the thing I do mostly
00:43:07.920
is form objects and I have my own gem mini form which is basically the same
00:43:13.800
thing as active model model it just has some nice goodies which I have seen a
00:43:19.640
lot of projects when they basically have an application form which is their own version of action model and they compile
00:43:28.240
like different parts what they need and I think that's something good that people should do uh one area here which
00:43:35.559
I personally also like is uh and I have noticed a lot of people still still have
00:43:41.559
it in the controllers they need to fil all the fields but often you need one form per One
00:43:47.720
controller and often I have this method that I call submit and subit underscore where it's like I actually guessed what
00:43:54.400
are the permit required for params so I never I just get the params to the form
00:44:01.680
I don't need to think about oh how is the form named what's in this form if I had a new field I have to go not only to
00:44:08.480
the form UI I need to go to the controller I need to list it there I need to change like five things on the pipeline I just usually I just say okay
00:44:16.160
just get me all the attributes names from this particular form and I care about that the form is my shield from
00:44:22.079
like all the fields and it works well most uh because
00:44:27.800
the the form is like a nice shoot it's not you are not calling the model directly plus I I I I change this
00:44:35.839
default option in rails every form has an S field and by default the form field
00:44:42.160
is the name of the model it's like let's say projects and it's name project let's
00:44:47.760
say it's account template it's account template and I have found this very unuseful for me because every time I
00:44:54.480
change the model name or I change the form I need to go to five places and change the params whatever thingy so all
00:45:01.920
my forms basically the form the input form is form because why not never seen
00:45:09.040
something it's very simple it works quite well and yeah and and the other thing
00:45:15.599
with the forms is I can just have my controllers mostly look like that I can
00:45:21.520
say okay this is a calendar event controller so I this controller so I can
00:45:27.319
just say Okay create me a form of the ATD with an event I can
00:45:33.280
do okay get me the calendar ATD form with like find event I can say a submit
00:45:39.280
the submit would get the params directly gets the params you don't have a separate method which lists all the
00:45:45.000
params with all the fields and again I have the find event here which uses the
00:45:50.079
F tracker to make sure the current user can actually manage this event and I use
00:45:56.079
this very old extracted from where yeah does that work with like more oh yeah
00:46:03.599
like my version the one I use in my application works with the like deep nestings and it validates the
00:46:08.880
keys I didn't show the whole code because it's like 30 lines and it's to early in the morning and this is non
00:46:14.240
alcoholic yet so it's uh but yeah it also I have I show I can show the
00:46:19.400
version with like the the B big deep nesting because I also have like delegations and things like that
00:46:25.079
connected with the thing but another another thing I use I think I'm the only one still using the gem responders from
00:46:31.160
like 200 years ago which was part of real then they remove it but I still really like this respond withd because
00:46:38.520
what respond withd does is it checks the record and if the error if the record
00:46:43.800
has validation errors it renders the error page if it doesn't have validation
00:46:49.040
errors it just goes to this location and it's like how many times do I need to write if
00:46:55.680
valid uh remember that so I just have this it's it's a bit of magical but I
00:47:01.559
still like it if this gem stop working I'll just in line it and use it myself
00:47:08.359
huh controller I if I need it I would do it like this is like really and also
00:47:13.760
this the other nice thing about this gem is it automatically also sets The Flash message and because it automatically in
00:47:20.319
my application particularly all the flash messages are connected to the internalization system so I actually
00:47:27.240
have flash message This Record was created and it's already translated and it all works and I don't need to think
00:47:32.680
about all the namings and when new developer starts working on my project they don't need to think about what's my
00:47:39.400
naming schedule for Flash events that that what would happen is they're going to implement this it's going to blow up
00:47:45.119
and tell them you don't have this key registered and they just would register the key and then they would
00:47:51.400
automatically do translations and it will be translated into five other languages and who cares
00:47:57.760
yeah but that's the thing what I do is I do I found out we talk about in the real Community a lot about the service
00:48:03.680
objects and not so much about the form objects and actually the form objects are I think the one separation between
00:48:10.240
like a service object and a form object is I think very important because the form object deals with like the user
00:48:15.920
input and it packages it for the user it has a lot which active model is really
00:48:21.559
great at and the service object is something that more okay doesn't have to
00:48:26.960
200 error States is just a function and operation and having this separation is
00:48:32.880
very useful uh like for example service objects often times are call from active jobs or like some external thing while
00:48:40.200
the form objects always work from like a user input also I have like a graph API
00:48:45.640
and the graph mutations are perfect for form objects I often in my previous company we had form objects for a UI
00:48:53.319
form in the admin and we used the same form object for for a graph mutation and they map very well to
00:49:00.480
that so yeah oh I'm getting to the end and it's almost two minutes left so
00:49:07.400
query object so often this is another thing often we need to build stuff like
00:49:13.400
that this is for my application when we have this very complex search search form we have some statistics for that
00:49:20.760
search and we have search results and this is a gem I created like 15 years
00:49:25.960
ago really literally 15 years ago it's called search object I'm very creative with names if you notice uh so search
00:49:34.200
object allows you to create like this form is basically search Finance transaction search filters params
00:49:41.520
results and usually if you need to implement an object like this I used to do like this 15 years ago I create this
00:49:48.960
class I get the filters and I basically do this if the filter is this just
00:49:54.480
reiterate to the scope and and get me like pagination like add me the pages
00:50:00.680
here and and again cat me the results because
00:50:06.359
again the results if I call it 20 times I just want one query so I started with this like 15 years ago I build this into
00:50:13.319
a gem where it's like I include the search object with kaminari for pagination I set the initial scope I get
00:50:21.400
the options and I have more again this is how we get the options it's basically the same same
00:50:27.960
thing and also this is actually dady added this 20 12 years ago you added
00:50:33.280
this feature the width yeah you added the width and the nice thing about this
00:50:38.440
having this object even if you don't use my gym if you just use the like you write this by yourself having an object
00:50:44.839
having a place to put stuff on you can add methods for oh give me the balance give me the income give me the expense
00:50:51.559
give me the count like this part you can just add it to your classes you don't need like Library you can just have like
00:50:58.079
a class that combines those searches and it can give you the statistics B based
00:51:03.520
on all those filters also if you have more advanced forms those forms have dropdowns and for example having this
00:51:10.280
class I can actually put in this class this is the cashier options this is the source options this is the type options
00:51:16.640
and having all of this in a central place in this search object is very useful to build it everywhere and yeah I
00:51:23.040
right now in my startup I use it a lot for UI forms the one I showed you and the nice thing is if you have this you
00:51:29.760
can actually build table in UI across of that because it's like a static right uh
00:51:34.920
it's like a standardized also I have used the same strategy with search object for apis like if you have like an
00:51:41.480
API or graph API you can have those composition of search objects so this is
00:51:47.440
another thing which is is very useful to think about like okay in a rilos project
00:51:52.599
this is all the things we have so yeah this is again in most ra project you
00:51:57.799
everybody has variations of those things and the big question is where do those things live I think this is another
00:52:05.119
thing so if you think about it what I told you today maybe in my app I have app policies services forms and queries
00:52:11.040
and that's great and that's great but I have other projects like I
00:52:18.920
have let's say I have the external stuff which I would name it app Network because this goes to the network oh I
00:52:26.200
have the validators as well maybe we have decorators maybe we have presenters because you know the big the big
00:52:31.920
difference between presenters decorator they shouldn't be mixed because people get confused uh we also have notifiers
00:52:37.799
for like notifications oh we have up values because maybe we have some value objects and we have heard it's a very
00:52:43.760
useful thing also maybe we need some support code like I have a library internal library for my project called
00:52:49.440
angry support for like the support Library also maybe ERS is also useful
00:52:55.760
because sometimes you don't know where to put stuff in that and again it's always a lot of discussions where to put
00:53:01.720
stuff and again for me it was always like oh my God and it's like oh we should put
00:53:08.040
everything in one folder like oh man this is such a mess then it's like okay put every object in their own folder it
00:53:15.119
becomes more messy and again I'm back to everything in one folder what I do in
00:53:20.480
all my projects right now is basically I have up lip so I move the lip from like down there to uplip because it's I think
00:53:27.480
very important and I use aggressive namespacing for the domain so for example I have search if you notied I
00:53:34.760
had the finance transaction search object I didn't have search transactions
00:53:39.960
I I start with the domain because it was very useful because when I go to my finance name space I see oh transaction
00:53:46.599
search transaction form transaction edit transaction edit whatever whatever now I
00:53:51.839
might maybe have transaction Finance transaction and I can group all those things so I have this and and this is
00:53:58.520
what right now how everything looks in my lip folder you you can notice my
00:54:03.839
domain I have the accounts I have the angry batch I have Angry support Apartments external export funds graph
00:54:12.359
heating which will be very useful right now if I look at that messaging payment
00:54:18.880
uh registration schedule search and all the other stuff but it's here by domain so when a developer starts thinking
00:54:25.839
about stuff they can do the fuzzy Search and say oh I search for the form object but it's Finance so I do Finance form and it
00:54:33.000
leaves me all the forms and yeah it's like a lot of like the YOLO kind of like everything is there everything is great
00:54:39.480
and everybody's so happy so yeah this is a lot of the stuff which again I was like okay every time I start a new rails
00:54:46.400
project I'm going to the slides and just copy pasting stuff because I don't do
00:54:51.520
rails project that often because it's so much work to copy paste all those settings but those I found like a lot of
00:54:58.599
like the stuff that's kind of like the missing parts and yeah that's pretty much all and I'm done on time
