{"id":7878,"date":"2021-02-12T00:00:00","date_gmt":"2021-02-11T23:00:00","guid":{"rendered":"https:\/\/blog.ouidou.fr\/?p=7878"},"modified":"2024-08-26T11:31:51","modified_gmt":"2024-08-26T09:31:51","slug":"rails-6-1-et-ses-nouveautes-notables","status":"publish","type":"post","link":"https:\/\/ouidou.fr\/blog\/articles-techniques\/rails-6-1-et-ses-nouveautes-notables","title":{"rendered":"Rails 6.1 et ses nouveaut\u00e9s notables"},"content":{"rendered":"<p><em>Article \u00e9crit par Nicolas Cavigneaux<\/em><\/p>\n<p>En d\u00e9cembre 2020, Rails 6.1 a \u00e9t\u00e9 publi\u00e9. Cette nouvelle version propose quelques nouveaut\u00e9s tr\u00e8s int\u00e9ressantes et qui selon moi font avancer Rails dans le bon sens.<\/p>\n<p>Nous allons passer en revue quatre de ces nouveaut\u00e9s qui ont retenu mon attention. Nous allons pr\u00e9senter\u00a0:<\/p>\n<ul>\n<li>le chargement strict des associations<\/li>\n<li>les types d\u00e9l\u00e9gu\u00e9s<\/li>\n<li>les objets d\u2019erreur<\/li>\n<li>la gestion des d\u00e9pr\u00e9ciations stricte<\/li>\n<\/ul>\n<h2 id=\"chargement-strict-des-associations\">Chargement strict des associations<\/h2>\n<p>Si j\u2019ai d\u00e9cid\u00e9 de parler de ce point en premier c\u2019est parce qu\u2019il me semble \u00eatre de loin l\u2019avanc\u00e9e la plus importante.<\/p>\n<p>Depuis aussi loin que Rails existe il a toujours \u00e9t\u00e9 possible d\u2019acc\u00e9der, sans c\u00e9r\u00e9monie, aux associations d\u2019un objet donn\u00e9.<\/p>\n<p>Disons que vous ayez des utilisateurs qui ont eux m\u00eame des billets de blog associ\u00e9s. Si vous souhaitez lister l\u2019ensemble des auteurs suivi de leurs billets respectifs vous pouvez faire la chose suivante\u00a0:<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"c1\"># app\/models\/user.rb<\/span> <span class=\"k\">class<\/span> <span class=\"nc\">User<\/span> <span class=\"o\">&lt;<\/span> <span class=\"no\">ApplicationRecord<\/span>   <span class=\"n\">has_many<\/span> <span class=\"ss\">:posts<\/span> <span class=\"k\">end<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"c1\"># app\/controllers\/users_controller.rb<\/span> <span class=\"k\">class<\/span> <span class=\"nc\">UsersController<\/span> <span class=\"o\">&lt;<\/span> <span class=\"no\">ApplicationController<\/span>   <span class=\"k\">def<\/span> <span class=\"nf\">index<\/span>     <span class=\"vi\">@users<\/span> <span class=\"o\">=<\/span> <span class=\"no\">User<\/span><span class=\"p\">.<\/span><span class=\"nf\">all<\/span>   <span class=\"k\">end<\/span> <span class=\"k\">end<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>Puis dans la vue associ\u00e9e \u00e0 cette action\u00a0:<\/p>\n<div class=\"language-erb highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"c\">&lt;!-- app\/views\/users\/index.html.erb` --&gt;<\/span> <span class=\"cp\">&lt;%<\/span> <span class=\"vi\">@users<\/span><span class=\"p\">.<\/span><span class=\"nf\">each<\/span> <span class=\"k\">do<\/span> <span class=\"o\">|<\/span><span class=\"n\">user<\/span><span class=\"o\">|<\/span> <span class=\"cp\">%&gt;<\/span> <span class=\"nt\">&lt;h2&gt;<\/span><span class=\"cp\">&lt;%=<\/span> <span class=\"n\">user<\/span><span class=\"p\">.<\/span><span class=\"nf\">full_name<\/span> <span class=\"cp\">%&gt;<\/span><span class=\"nt\">&lt;\/h2&gt;<\/span> <span class=\"nt\">&lt;ul&gt;<\/span>   <span class=\"cp\">&lt;%<\/span> <span class=\"n\">user<\/span><span class=\"p\">.<\/span><span class=\"nf\">posts<\/span><span class=\"p\">.<\/span><span class=\"nf\">each<\/span> <span class=\"k\">do<\/span> <span class=\"o\">|<\/span><span class=\"n\">post<\/span><span class=\"o\">|<\/span> <span class=\"cp\">%&gt;<\/span>   <span class=\"nt\">&lt;li&gt;<\/span><span class=\"cp\">&lt;%=<\/span> <span class=\"n\">post<\/span><span class=\"p\">.<\/span><span class=\"nf\">title<\/span> <span class=\"cp\">%&gt;<\/span><span class=\"nt\">&lt;\/li&gt;<\/span>   <span class=\"cp\">&lt;%<\/span> <span class=\"k\">end<\/span> <span class=\"cp\">%&gt;<\/span> <span class=\"nt\">&lt;\/ul&gt;<\/span> <span class=\"cp\">&lt;%<\/span> <span class=\"k\">end<\/span> <span class=\"cp\">%&gt;<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>Ce code est fonctionnel, vous aurez bien le r\u00e9sultat attendu soit la liste des utilisateurs avec leurs billets respectifs.<\/p>\n<p>C\u2019est donc tout ce qu\u2019il y a de plus simple \u00e0 mettre en \u0153uvre. Alors que peut-on bien apporter comme am\u00e9lioration \u00e0 un code si limpide et facile \u00e0 \u00e9crire\u00a0?<\/p>\n<p>On peut apporter un gain de performance\u00a0! En \u00e9crivant le code ci-dessus vous venez d\u2019introduire une requ\u00eate N+1. Chaque fois qu\u2019un utilisateur chargera cette page une requ\u00eate SQL sera ex\u00e9cut\u00e9e pour r\u00e9cup\u00e9rer la liste des utilisateurs. Puis \u00e0 l\u2019affichage de chaque utilisateur, Rails effectuera une requ\u00eate SQL suppl\u00e9mentaire pour r\u00e9cup\u00e9rer la liste des billets de l\u2019utilisateur en cours d\u2019it\u00e9ration.<\/p>\n<p>Donc si on liste ici 100 utilisateurs, Rails va, <strong>sans rien nous demander<\/strong>, lancer <strong>100<\/strong> requ\u00eates SQL suppl\u00e9mentaire.<\/p>\n<p>C\u2019est un <strong>gouffre<\/strong> \u00e0 performance. Il est tout \u00e0 fait possible en SQL, et via ActiveRecord, de r\u00e9cup\u00e9rer l\u2019ensemble de ces informations en seulement 2 requ\u00eates. Peu importe qu\u2019on souhaite lister 4 utilisateurs, 100 ou 10\u00a0000.<\/p>\n<h3 id=\"avant-rails-61\">Avant Rails 6.1<\/h3>\n<p>\u00c9tant bien \u00e9videmment au fait de ce souci, l\u2019\u00e9quipe de Rails a mis \u00e0 disposition une m\u00e9thode qu\u2019on peut appeler sur nos relations pour indiquer \u00e0 ActiveRecord de se comporter intelligemment et d\u2019optimiser ce genre de requ\u00eate\u00a0:<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"k\">class<\/span> <span class=\"nc\">UsersController<\/span> <span class=\"o\">&lt;<\/span> <span class=\"no\">ApplicationController<\/span>   <span class=\"k\">def<\/span> <span class=\"nf\">index<\/span>     <span class=\"vi\">@users<\/span> <span class=\"o\">=<\/span> <span class=\"no\">User<\/span><span class=\"p\">.<\/span><span class=\"nf\">includes<\/span><span class=\"p\">(<\/span><span class=\"ss\">:posts<\/span><span class=\"p\">).<\/span><span class=\"nf\">all<\/span>   <span class=\"k\">end<\/span> <span class=\"k\">end<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>D\u00e8s lors, plus de probl\u00e8me de requ\u00eates N+1, ActiveRecord prendra soin de faire une requ\u00eate pour r\u00e9cup\u00e9rer les utilisateurs puis <strong>une seule<\/strong> autre pour r\u00e9cup\u00e9rer l\u2019ensemble des billets associ\u00e9s \u00e0 ces utilisateurs et d\u2019en faire le mapping.<\/p>\n<p>On peut \u00e9videmment inclure plus d\u2019une association ou m\u00eame le faire en cascade\u00a0:<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"no\">User<\/span><span class=\"p\">.<\/span><span class=\"nf\">includes<\/span><span class=\"p\">(<\/span><span class=\"ss\">:friends<\/span><span class=\"p\">,<\/span> <span class=\"ss\">posts: <\/span><span class=\"p\">[<\/span><span class=\"ss\">:comments<\/span><span class=\"p\">]).<\/span><span class=\"nf\">all<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>On est donc sauf, on a l\u2019outillage pour faire les choses bien\u00a0! Oui mais\u2026 parce qu\u2019il y a un \u00ab\u00a0mais\u00a0\u00bb. Nous sommes des \u00eatres humains et nous faisons des erreurs, des oublis\u2026<\/p>\n<p>Si quelqu\u2019un dans l\u2019\u00e9quipe oubli de g\u00e9rer ce genre de cas et que le code part en production, vous vous retrouvez avec des N+1. Et croyez-moi, \u00e7a y restera jusqu\u2019\u00e0 ce que quelqu\u2019un s\u2019en rende compte par hasard, que le client se plaigne de l\u2019extr\u00eame lenteur de chargement de la page X ou que vous mettiez en place un outil dont le but est de rep\u00e9rer les N+1.<\/p>\n<h3 id=\"depuis-rails-61\">Depuis Rails 6.1<\/h3>\n<p>Fort heureusement, <a href=\"https:\/\/github.com\/eileencodes\">Eileen M. Uchitelle<\/a> de chez GitHub a eu la bonne id\u00e9e de proposer une nouvelle fonctionnalit\u00e9 pour s\u2019assurer de ne plus louper d\u2019\u00e9ventuelles N+1 introduites par une boucle dans une vue au d\u00e9tour d\u2019une demande fonctionnelle anodine.<\/p>\n<p>Le principe de <em>Strict Loading Associations<\/em> permet de s\u2019assurer que toutes les associations sont pr\u00e9-charg\u00e9es et donc \u00e9viter l\u2019apparition de N+1.<\/p>\n<p>On peut maintenant pr\u00e9ciser sur une relation qu\u2019on souhaite avoir du chargement strict et lever une exception en cas de tentative de <em>lazy loading<\/em>. On pourra par exemple faire la chose suivante\u00a0:<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"n\">user<\/span> <span class=\"o\">=<\/span> <span class=\"no\">User<\/span><span class=\"p\">.<\/span><span class=\"nf\">strict_loading<\/span><span class=\"p\">.<\/span><span class=\"nf\">first<\/span> <span class=\"n\">user<\/span><span class=\"p\">.<\/span><span class=\"nf\">posts<\/span>  <span class=\"c1\"># =&gt; ActiveRecord::StrictLoadingViolationError:<\/span> <span class=\"c1\">#    User is marked as strict_loading and AuditLog cannot be lazily loaded.<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>D\u00e8s que nous allons essayer d\u2019acc\u00e9der \u00e0 une association qui n\u2019est pas pr\u00e9-charg\u00e9e (\u00e0 l\u2019aide de <code>includes<\/code>), une exception est lev\u00e9e ce qui facilite sa d\u00e9couverte lors du d\u00e9veloppement ou encore dans les tests.<\/p>\n<p>C\u2019est d\u00e9j\u00e0 un pas en avant\u00a0! Pour autant il ne faut pas oublier d\u2019appeler <code>strict_loading<\/code> sur notre relation avant de l\u2019utiliser sans quoi on pourra toujours charger les relations \u00e0 la vol\u00e9e.<\/p>\n<p>Une premi\u00e8re solution consiste \u00e0 cr\u00e9er un scope qui force le <em>strict loading<\/em> sur une association donn\u00e9e\u00a0:<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"k\">class<\/span> <span class=\"nc\">User<\/span> <span class=\"o\">&lt;<\/span> <span class=\"no\">ApplicationRecord<\/span>   <span class=\"n\">has_many<\/span> <span class=\"ss\">:strict_loading_posts<\/span><span class=\"p\">,<\/span> <span class=\"o\">-&gt;<\/span> <span class=\"p\">{<\/span> <span class=\"n\">strict_loading<\/span> <span class=\"p\">},<\/span> <span class=\"ss\">class_name: <\/span><span class=\"s2\">\"Post\"<\/span> <span class=\"k\">end<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>C\u2019est mieux mais \u00e7a peut vite devenir contraignant et r\u00e9p\u00e9titif si on a beaucoup de relations. Mais une fois de plus la communaut\u00e9 vient \u00e0 notre rescousse gr\u00e2ce \u00e0 Kevin Newton de chez Shopify qui a introduit une option sur la d\u00e9claration des associations pour faciliter ce travail\u00a0:<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"k\">class<\/span> <span class=\"nc\">User<\/span> <span class=\"o\">&lt;<\/span> <span class=\"no\">ApplicationRecord<\/span>   <span class=\"n\">has_many<\/span> <span class=\"ss\">:posts<\/span><span class=\"p\">,<\/span> <span class=\"ss\">strict_loading: <\/span><span class=\"kp\">true<\/span> <span class=\"k\">end<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>De mieux en mieux\u00a0! Mais je vous vois venir, d\u00e9veloppeurs fain\u00e9ants que vous \u00eates\u00a0! Vous voulez que tout \u00e7a soit automatique, sur toutes vos associations\u00a0?<\/p>\n<p>Eh bien vous avez \u00e9t\u00e9 entendus\u00a0! Voici comment faire\u00a0:<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"k\">class<\/span> <span class=\"nc\">User<\/span> <span class=\"o\">&lt;<\/span> <span class=\"no\">ApplicationRecord<\/span>   <span class=\"nb\">self<\/span><span class=\"p\">.<\/span><span class=\"nf\">strict_loading_by_default<\/span> <span class=\"o\">=<\/span> <span class=\"kp\">true<\/span>    <span class=\"n\">has_many<\/span> <span class=\"ss\">:posts<\/span> <span class=\"k\">end<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>Maintenant toutes les associations du mod\u00e8le <code>User<\/code> seront soumises au <em>strict loading<\/em>.<\/p>\n<p>Et je vois venir les plus vicieux d\u2019entre vous, non il n\u2019y a pas (encore) d\u2019option globale pour faire en sorte que ce soit le comportement de tous les mod\u00e8les.<\/p>\n<p>Mais deux solutions s\u2019offrent \u00e0 vous. La premi\u00e8re, proposer un patch et devenir core contributor Rails\u00a0! Sinon vous pouvez simplement d\u00e9finir le <em>strict loading<\/em> directement dans <code>ApplicationRecord<\/code>. De ce fait, tous les mod\u00e8les qui en h\u00e9ritent utiliseront le <em>strict loading<\/em> :<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"k\">class<\/span> <span class=\"nc\">ApplicationRecord<\/span> <span class=\"o\">&lt;<\/span> <span class=\"no\">ActiveRecord<\/span><span class=\"o\">::<\/span><span class=\"no\">Base<\/span>   <span class=\"nb\">self<\/span><span class=\"p\">.<\/span><span class=\"nf\">abstract_class<\/span> <span class=\"o\">=<\/span> <span class=\"kp\">true<\/span>   <span class=\"nb\">self<\/span><span class=\"p\">.<\/span><span class=\"nf\">strict_loading_by_default<\/span> <span class=\"o\">=<\/span> <span class=\"kp\">true<\/span> <span class=\"k\">end<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<h2 id=\"les-types-dlgus\">Les types d\u00e9l\u00e9gu\u00e9s<\/h2>\n<h3 id=\"avant-rails-61-1\">Avant Rails 6.1<\/h3>\n<p>Jusqu\u2019\u00e0 maintenant quand on souhaitait agr\u00e9ger plusieurs mod\u00e8les autour d\u2019une m\u00eame table en base de donn\u00e9e et d\u2019un m\u00eame mod\u00e8le de base parce qu\u2019une grande majorit\u00e9 des donn\u00e9es et comportements \u00e9taient communs, on avait tendance \u00e0 se tourner vers le <a href=\"https:\/\/api.rubyonrails.org\/classes\/ActiveRecord\/Inheritance.html\">STI<\/a>.<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"k\">class<\/span> <span class=\"nc\">Company<\/span> <span class=\"o\">&lt;<\/span> <span class=\"no\">ApplicationRecord<\/span><span class=\"p\">;<\/span> <span class=\"k\">end<\/span> <span class=\"k\">class<\/span> <span class=\"nc\">Firm<\/span> <span class=\"o\">&lt;<\/span> <span class=\"no\">Company<\/span><span class=\"p\">;<\/span> <span class=\"k\">end<\/span> <span class=\"k\">class<\/span> <span class=\"nc\">Client<\/span> <span class=\"o\">&lt;<\/span> <span class=\"no\">Company<\/span><span class=\"p\">;<\/span> <span class=\"k\">end<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>Ici toutes les informations, qu\u2019elles soient cr\u00e9\u00e9es \u00e0 travers le mod\u00e8le <code>Company<\/code>, <code>Firm<\/code> ou <code>Client<\/code> seront stock\u00e9es dans la table <code>companies<\/code> avec une colonne <code>type<\/code> qui permettra de savoir \u00e0 quel mod\u00e8le appartient l\u2019enregistrement.<\/p>\n<p><code>Company<\/code> permet d\u2019acc\u00e9der \u00e0 l\u2019ensemble des donn\u00e9es sans distinction de type.<\/p>\n<p>Cette solution peut \u00eatre tr\u00e8s pratique mais est, \u00e0 mon sens, \u00e0 r\u00e9server \u00e0 des cas bien ma\u00eetris\u00e9s pour lesquels on sait que les \u00e9volutions seront contenues et majoritairement transverses au mod\u00e8le de base du STI.<\/p>\n<p>Si vos mod\u00e8les \u00ab\u00a0enfants\u00a0\u00bb vivent tous leur vie et commencent tous \u00e0 impl\u00e9menter des comportements sp\u00e9cifiques avec tout un tas de colonnes sp\u00e9cifiques, votre code et votre table vont vite devenir brouillons.<\/p>\n<p>Alors de deux choses l\u2019une\u00a0: soit vous revoyez toute votre architecture ainsi que l\u2019essence m\u00eame du mantra DRY, soit\u2026<\/p>\n<h3 id=\"depuis-rails-61-1\">Depuis Rails 6.1<\/h3>\n<p>C\u2019est pour <a href=\"https:\/\/github.com\/rails\/rails\/pull\/39341\">proposer une alternative<\/a> plus \u00e9volutive et d\u00e9coupl\u00e9e que <a href=\"https:\/\/github.com\/dhh\">DHH<\/a> a ajout\u00e9 les types d\u00e9l\u00e9gu\u00e9s.<\/p>\n<p>Les <a href=\"https:\/\/api.rubyonrails.org\/v6.1.0\/classes\/ActiveRecord\/DelegatedType.html\">types d\u00e9l\u00e9gu\u00e9s<\/a> vont nous permettre de repr\u00e9senter une hi\u00e9rarchie de classes avec un parent commun qui poss\u00e8de sa propre table. Chaque enfant poss\u00e9dera sa table d\u00e9di\u00e9e pour y stocker ses attributs sp\u00e9cifiques.<\/p>\n<p>Voyons comment mettre en place le mod\u00e8le parent\u00a0:<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"k\">class<\/span> <span class=\"nc\">Company<\/span> <span class=\"o\">&lt;<\/span> <span class=\"no\">ApplicationRecord<\/span>   <span class=\"n\">delegated_type<\/span> <span class=\"ss\">:structure<\/span><span class=\"p\">,<\/span> <span class=\"ss\">types: <\/span><span class=\"sx\">%w(Firm Client)<\/span>    <span class=\"c1\"># Code commun \u00e0 tous<\/span>   <span class=\"c1\"># \u00c9ventuellement des d\u00e9l\u00e9gations (ie: delegates :owner, to: :companyable)<\/span> <span class=\"k\">end<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>Cette classe s\u2019attend \u00e0 trouver une table <code>companies<\/code> dans laquelle il y aura, entre autres, les colonnes <code>structure_type<\/code> et <code>structure_id<\/code>. Pour ceux qui ont suivi, c\u2019est tout simplement une <a href=\"https:\/\/guides.rubyonrails.org\/association_basics.html#polymorphic-associations\">association polymorphique<\/a>.<\/p>\n<p>Cette classe d\u00e9finie ensuite les enfants qui vont lui \u00eatre associ\u00e9s, ici <code>Firm<\/code> et <code>Client<\/code>.<\/p>\n<p>Il ne reste plus qu\u2019\u00e0 d\u00e9clarer nos mod\u00e8les enfant et les rattacher \u00e0 leur parent\u00a0:<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"k\">class<\/span> <span class=\"nc\">Firm<\/span> <span class=\"o\">&lt;<\/span> <span class=\"no\">ApplicationRecord<\/span>   <span class=\"n\">has_one<\/span> <span class=\"ss\">:company<\/span><span class=\"p\">,<\/span> <span class=\"ss\">as: :structure<\/span><span class=\"p\">,<\/span> <span class=\"ss\">touch: <\/span><span class=\"kp\">true<\/span>    <span class=\"k\">def<\/span> <span class=\"nf\">owner<\/span>     <span class=\"c1\"># une fa\u00e7on de r\u00e9cup\u00e9rer l'info<\/span>   <span class=\"k\">end<\/span> <span class=\"k\">end<\/span>  <span class=\"k\">class<\/span> <span class=\"nc\">Client<\/span> <span class=\"o\">&lt;<\/span> <span class=\"no\">ApplicationRecord<\/span>   <span class=\"n\">has_one<\/span> <span class=\"ss\">:company<\/span><span class=\"p\">,<\/span> <span class=\"ss\">as: :structure<\/span><span class=\"p\">,<\/span> <span class=\"ss\">touch: <\/span><span class=\"kp\">true<\/span>    <span class=\"k\">def<\/span> <span class=\"nf\">owner<\/span>     <span class=\"c1\"># une autre fa\u00e7on<\/span>   <span class=\"k\">end<\/span> <span class=\"k\">end<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>On peut d\u00e9sormais se servir de nos classes pour g\u00e9rer notre hi\u00e9rarchie et d\u00e9l\u00e9guer les comportements sp\u00e9cifiques \u00e0 la classe appropri\u00e9e.<\/p>\n<p>On cr\u00e9e d\u2019abord une entr\u00e9e\u00a0:<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"no\">Company<\/span><span class=\"p\">.<\/span><span class=\"nf\">create<\/span> <span class=\"ss\">structure: <\/span><span class=\"no\">Firm<\/span><span class=\"p\">.<\/span><span class=\"nf\">new<\/span><span class=\"p\">(<\/span><span class=\"ss\">employees_count: <\/span><span class=\"mi\">200<\/span><span class=\"p\">),<\/span> <span class=\"ss\">name: <\/span><span class=\"s2\">\"Foo Bar Corp\"<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"no\">Company<\/span><span class=\"p\">.<\/span><span class=\"nf\">firms<\/span> <span class=\"c1\"># Relation retournant toutes les entr\u00e9es de type \"firm\"<\/span> <span class=\"no\">Company<\/span><span class=\"p\">.<\/span><span class=\"nf\">first<\/span><span class=\"p\">.<\/span><span class=\"nf\">firm?<\/span> <span class=\"c1\"># Est-ce une instance de Firm ?<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>Vos diff\u00e9rents mod\u00e8les sont donc des mod\u00e8les \u00e0 part enti\u00e8re, ind\u00e9pendants, avec leurs attributs propres, leur table d\u00e9di\u00e9e mais qui s\u2019inscrivent dans une hi\u00e9rarchie avec un parent qui regroupe les informations et fonctionnalit\u00e9s communes.<\/p>\n<h2 id=\"les-objets-derreur\">Les objets d\u2019erreur<\/h2>\n<p>Lorsqu\u2019un objet ActiveRecord est soumis \u00e0 validation, son attribut <code>errors<\/code> est rempli si n\u00e9cessaire, avec une structure certes norm\u00e9e mais ne b\u00e9n\u00e9ficiant d\u2019aucun traitement particulier nous permettant de le manipuler facilement.<\/p>\n<p>C\u2019est pourtant une information avec laquelle on interagit tr\u00e8s souvent et que nous devons manipuler pour l\u2019affichage, la structuration des r\u00e9ponses JSON, les v\u00e9rifications annexes\u2026<\/p>\n<p>Rails 6.1 introduit la notion de <em>error object<\/em> qui met \u00e0 disposition <a href=\"https:\/\/api.rubyonrails.org\/classes\/ActiveModel\/Error.html\">une interface<\/a> qui consiste \u00e0 utiliser un objet d\u00e9di\u00e9 pour chaque entr\u00e9e du tableau d\u2019erreurs.<\/p>\n<p>Cette nouvelle interface facilite la manipulation et les interactions avec les erreurs remont\u00e9es par les mod\u00e8les.<\/p>\n<p>Une erreur peut \u00eatre instanci\u00e9e de la fa\u00e7on suivante\u00a0:<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"n\">error<\/span> <span class=\"o\">=<\/span> <span class=\"no\">ActiveModel<\/span><span class=\"o\">::<\/span><span class=\"no\">Error<\/span><span class=\"p\">.<\/span><span class=\"nf\">new<\/span><span class=\"p\">(<\/span><span class=\"n\">user<\/span><span class=\"p\">,<\/span> <span class=\"ss\">:name<\/span><span class=\"p\">,<\/span> <span class=\"ss\">:too_short<\/span><span class=\"p\">,<\/span> <span class=\"ss\">count: <\/span><span class=\"mi\">5<\/span><span class=\"p\">)<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>Puis \u00eatre requ\u00eat\u00e9e\u00a0:<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"n\">error<\/span><span class=\"p\">.<\/span><span class=\"nf\">details<\/span> <span class=\"c1\"># =&gt; { error: :too_short, count: 5 }<\/span> <span class=\"n\">error<\/span><span class=\"p\">.<\/span><span class=\"nf\">full_message<\/span> <span class=\"c1\"># =&gt; \"Name is too short (minimum is 5 characters)\"<\/span> <span class=\"n\">error<\/span><span class=\"p\">.<\/span><span class=\"nf\">match?<\/span><span class=\"p\">(<\/span><span class=\"ss\">:name<\/span><span class=\"p\">,<\/span> <span class=\"ss\">:too_short<\/span><span class=\"p\">)<\/span> <span class=\"c1\"># =&gt; true<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>On peut \u00e9galement requ\u00eater et manipuler <a href=\"https:\/\/api.rubyonrails.org\/classes\/ActiveModel\/Errors.html\">la liste des erreurs<\/a> :<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"n\">model<\/span><span class=\"p\">.<\/span><span class=\"nf\">errors<\/span><span class=\"p\">.<\/span><span class=\"nf\">where<\/span><span class=\"p\">(<\/span><span class=\"ss\">:name<\/span><span class=\"p\">,<\/span> <span class=\"ss\">:foo<\/span><span class=\"p\">,<\/span> <span class=\"ss\">bar: <\/span><span class=\"mi\">3<\/span><span class=\"p\">).<\/span><span class=\"nf\">first<\/span> <span class=\"n\">model<\/span><span class=\"p\">.<\/span><span class=\"nf\">errors<\/span><span class=\"p\">.<\/span><span class=\"nf\">delete<\/span><span class=\"p\">(<\/span><span class=\"ss\">:name<\/span><span class=\"p\">,<\/span> <span class=\"ss\">:too_powerful<\/span><span class=\"p\">,<\/span> <span class=\"ss\">level: <\/span><span class=\"mi\">9000<\/span><span class=\"p\">)<\/span>  <span class=\"n\">model<\/span><span class=\"p\">.<\/span><span class=\"nf\">errors<\/span><span class=\"p\">.<\/span><span class=\"nf\">added?<\/span><span class=\"p\">(<\/span><span class=\"ss\">:name<\/span><span class=\"p\">,<\/span> <span class=\"ss\">:too_powerful<\/span><span class=\"p\">,<\/span> <span class=\"ss\">level: <\/span><span class=\"mi\">9000<\/span><span class=\"p\">)<\/span> <span class=\"c1\"># false<\/span> <span class=\"n\">model<\/span><span class=\"p\">.<\/span><span class=\"nf\">errors<\/span><span class=\"p\">.<\/span><span class=\"nf\">add<\/span><span class=\"p\">(<\/span><span class=\"ss\">:name<\/span><span class=\"p\">,<\/span> <span class=\"ss\">:too_powerful<\/span><span class=\"p\">,<\/span> <span class=\"ss\">level: <\/span><span class=\"mi\">9000<\/span><span class=\"p\">)<\/span> <span class=\"n\">model<\/span><span class=\"p\">.<\/span><span class=\"nf\">errors<\/span><span class=\"p\">.<\/span><span class=\"nf\">added?<\/span><span class=\"p\">(<\/span><span class=\"ss\">:name<\/span><span class=\"p\">,<\/span> <span class=\"ss\">:too_powerful<\/span><span class=\"p\">)<\/span> <span class=\"c1\"># true<\/span>  <span class=\"n\">model<\/span><span class=\"p\">.<\/span><span class=\"nf\">errors<\/span><span class=\"p\">.<\/span><span class=\"nf\">details<\/span> <span class=\"c1\"># =&gt; {:name=&gt;[{error: :too_short, count: 5}, {error: :cant_be_blank}]}<\/span>  <span class=\"n\">errors<\/span><span class=\"p\">.<\/span><span class=\"nf\">messages_for<\/span><span class=\"p\">(<\/span><span class=\"ss\">:name<\/span><span class=\"p\">)<\/span> <span class=\"c1\"># =&gt; [\"is too short (minimum is 5 characters)\", \"can't be blank\"]<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>Il est donc maintenant un peu plus facile d\u2019obtenir des informations concernant une erreur.<\/p>\n<h2 id=\"saffranchir-des-dprciations\">S\u2019affranchir des d\u00e9pr\u00e9ciations<\/h2>\n<p>Si vous aimez vous assurer que votre code n\u2019introduit pas d\u2019appels de m\u00e9thodes d\u00e9pr\u00e9ci\u00e9es dans votre application ou simplement que vous pr\u00e9parez une migration vers une version plus r\u00e9cente de Rails. La fonctionnalit\u00e9 suivante vous facilitera grandement la t\u00e2che.<\/p>\n<p>Jusqu\u2019\u00e0 maintenant les d\u00e9pr\u00e9ciations \u00e9taient logu\u00e9es, on peut maintenant lever une exception d\u00e8s qu\u2019une m\u00e9thode d\u00e9pr\u00e9ci\u00e9e est utilis\u00e9e dans notre code.<\/p>\n<p>Cette fonctionnalit\u00e9 est param\u00e9trable de mani\u00e8re flexible, on pourra donc faire en sorte d\u2019avoir un comportement diff\u00e9rent en mode d\u00e9veloppement et en mode production. On pourra aussi ne l\u2019activer que pour des \u00e9l\u00e9ments cibl\u00e9s.<\/p>\n<h3 id=\"configuration\">Configuration<\/h3>\n<p>Pour activer globalement la lev\u00e9e d\u2019exception lorsqu\u2019une m\u00e9thode d\u00e9pr\u00e9ci\u00e9e est rencontr\u00e9e, il suffira d\u2019utiliser\u00a0:<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"no\">ActiveSupport<\/span><span class=\"o\">::<\/span><span class=\"no\">Deprecation<\/span><span class=\"p\">.<\/span><span class=\"nf\">disallowed_warnings<\/span> <span class=\"o\">=<\/span> <span class=\"ss\">:all<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>Si vous voulez lever des exceptions uniquement en d\u00e9veloppement et test mais simplement loguer en production, on pourra utiliser\u00a0:<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"k\">if<\/span> <span class=\"no\">Rails<\/span><span class=\"p\">.<\/span><span class=\"nf\">env<\/span><span class=\"p\">.<\/span><span class=\"nf\">production?<\/span>   <span class=\"no\">ActiveSupport<\/span><span class=\"o\">::<\/span><span class=\"no\">Deprecation<\/span><span class=\"p\">.<\/span><span class=\"nf\">disallowed_behavior<\/span> <span class=\"o\">=<\/span> <span class=\"p\">[<\/span><span class=\"ss\">:log<\/span><span class=\"p\">]<\/span> <span class=\"k\">else<\/span>   <span class=\"no\">ActiveSupport<\/span><span class=\"o\">::<\/span><span class=\"no\">Deprecation<\/span><span class=\"p\">.<\/span><span class=\"nf\">disallowed_behavior<\/span> <span class=\"o\">=<\/span> <span class=\"p\">[<\/span><span class=\"ss\">:raise<\/span><span class=\"p\">]<\/span> <span class=\"k\">end<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>Si pour des raisons pratiques vous souhaitez autoriser temporairement l\u2019utilisation de m\u00e9thodes d\u00e9pr\u00e9ci\u00e9es dans votre code vous pourrez d\u00e9finir un bloc \u00e0 cet effet\u00a0:<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"no\">ActiveSupport<\/span><span class=\"o\">::<\/span><span class=\"no\">Deprecation<\/span><span class=\"p\">.<\/span><span class=\"nf\">allow<\/span> <span class=\"k\">do<\/span>   <span class=\"no\">User<\/span><span class=\"p\">.<\/span><span class=\"nf\">do_thing_that_calls_bad_and_worse_method<\/span> <span class=\"k\">end<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>On autorisera ici absolument toutes les m\u00e9thodes d\u00e9pr\u00e9ci\u00e9es mais la plupart du temps il sera plus judicieux de pr\u00e9ciser celles qu\u2019on veut autoriser\u00a0:<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"no\">ActiveSupport<\/span><span class=\"o\">::<\/span><span class=\"no\">Deprecation<\/span><span class=\"p\">.<\/span><span class=\"nf\">allow<\/span> <span class=\"p\">[<\/span><span class=\"ss\">:bad_method<\/span><span class=\"p\">,<\/span> <span class=\"s2\">\"worse_method\"<\/span><span class=\"p\">]<\/span> <span class=\"k\">do<\/span>   <span class=\"no\">User<\/span><span class=\"p\">.<\/span><span class=\"nf\">do_thing_that_calls_bad_and_worse_method<\/span> <span class=\"k\">end<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>L\u2019argument pass\u00e9 pour d\u00e9crire les m\u00e9thodes \u00e0 autoriser temporairement doit \u00eatre un tableau qui peut contenir des cha\u00eenes, des symboles ou encore des expressions rationnelles.<\/p>\n<p>Il est m\u00eame pr\u00e9vu de pouvoir passer une condition qui d\u00e9terminera si le bloc doit \u00eatre soumis \u00e0 la lev\u00e9e d\u2019exception ou non\u00a0:<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"no\">ActiveSupport<\/span><span class=\"o\">::<\/span><span class=\"no\">Deprecation<\/span><span class=\"p\">.<\/span><span class=\"nf\">allow<\/span> <span class=\"p\">[<\/span><span class=\"ss\">:bad_method<\/span><span class=\"p\">],<\/span> <span class=\"ss\">if: <\/span><span class=\"no\">Rails<\/span><span class=\"p\">.<\/span><span class=\"nf\">env<\/span><span class=\"p\">.<\/span><span class=\"nf\">production?<\/span> <span class=\"k\">do<\/span>   <span class=\"no\">User<\/span><span class=\"p\">.<\/span><span class=\"nf\">do_thing_that_calls_bad_method<\/span> <span class=\"k\">end<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>Pour finir il est possible de d\u00e9finir de mani\u00e8re tr\u00e8s fine les m\u00e9thodes que vous souhaitez traquer pour lever des exceptions\u00a0:<\/p>\n<div class=\"language-ruby highlighter-rouge\">\n<div class=\"highlight\">\n<pre class=\"highlight\"><code><span class=\"no\">ActiveSupport<\/span><span class=\"o\">::<\/span><span class=\"no\">Deprecation<\/span><span class=\"p\">.<\/span><span class=\"nf\">disallowed_warnings<\/span> <span class=\"o\">=<\/span> <span class=\"p\">[<\/span>   <span class=\"s2\">\"bad_method is deprecated\"<\/span><span class=\"p\">,<\/span>   <span class=\"ss\">:worse_method<\/span><span class=\"p\">,<\/span>   <span class=\"sr\">\/(horrible|unsafe)_method\/<\/span> <span class=\"p\">]<\/span> <\/code><\/pre>\n<\/div>\n<\/div>\n<p>Une fois encore le format attendu est un tableau pouvant contenir des cha\u00eenes, des symboles ou des expressions rationnelles.<\/p>\n<p>On a donc pu voir quatre ajouts fonctionnels qui ont \u00e9t\u00e9 faits \u00e0 Rails et qui selon moi m\u00e9ritent d\u2019\u00eatre essay\u00e9s. Ils vous aideront sans aucun doute \u00e0 produire du code plus robuste.<\/p>\n<p>D\u2019autres nouveaut\u00e9s et correctifs ont \u00e9t\u00e9 apport\u00e9es pour les d\u00e9couvrir je vous invite \u00e0 <a href=\"https:\/\/github.com\/rails\/rails\/blob\/v6.1.1\/activerecord\/CHANGELOG.md#rails-610-december-09-2020\">consulter le CHANGELOG<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Rails 6.1 est sorti il y a peu et avec lui un certain nombre de nouveaut\u00e9s tr\u00e8s int\u00e9ressantes que nous allons d\u00e9couvrir ensemble<\/p>\n","protected":false},"author":10,"featured_media":12518,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","inline_featured_image":false,"fifu_image_url":"","fifu_image_alt":"","footnotes":""},"categories":[34],"tags":[],"class_list":["post-7878","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-articles-techniques"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Rails 6.1 et ses nouveaut\u00e9s notables - Ouidou<\/title>\n<meta name=\"description\" content=\"Nos experts pr\u00e9sentent les nouveaut\u00e9s marquantes de Rails 6.1, am\u00e9liorant la gestion des donn\u00e9es et la s\u00e9curit\u00e9.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/ouidou.fr\/blog\/articles-techniques\/rails-6-1-et-ses-nouveautes-notables\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Rails 6.1 et ses nouveaut\u00e9s notables - Ouidou\" \/>\n<meta property=\"og:description\" content=\"Nos experts pr\u00e9sentent les nouveaut\u00e9s marquantes de Rails 6.1, am\u00e9liorant la gestion des donn\u00e9es et la s\u00e9curit\u00e9.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/ouidou.fr\/blog\/articles-techniques\/rails-6-1-et-ses-nouveautes-notables\" \/>\n<meta property=\"og:site_name\" content=\"Ouidou\" \/>\n<meta property=\"article:published_time\" content=\"2021-02-11T23:00:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2024-08-26T09:31:51+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/ouidou.fr\/blog\/wp-content\/uploads\/2021\/02\/Rails-6.1-et-ses-nouveaute\u0301s-notables.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1105\" \/>\n\t<meta property=\"og:image:height\" content=\"564\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Sara Lourties\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"Sara Lourties\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/articles-techniques\\\/rails-6-1-et-ses-nouveautes-notables#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/articles-techniques\\\/rails-6-1-et-ses-nouveautes-notables\"},\"author\":{\"name\":\"Sara Lourties\",\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/#\\\/schema\\\/person\\\/e1d66085fb7c22ede319ce56adc373a4\"},\"headline\":\"Rails 6.1 et ses nouveaut\u00e9s notables\",\"datePublished\":\"2021-02-11T23:00:00+00:00\",\"dateModified\":\"2024-08-26T09:31:51+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/articles-techniques\\\/rails-6-1-et-ses-nouveautes-notables\"},\"wordCount\":1901,\"publisher\":{\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/articles-techniques\\\/rails-6-1-et-ses-nouveautes-notables#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/02\\\/Rails-6.1-et-ses-nouveaute\u0301s-notables.png\",\"articleSection\":[\"Articles Techniques\"],\"inLanguage\":\"fr-FR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/articles-techniques\\\/rails-6-1-et-ses-nouveautes-notables\",\"url\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/articles-techniques\\\/rails-6-1-et-ses-nouveautes-notables\",\"name\":\"Rails 6.1 et ses nouveaut\u00e9s notables - Ouidou\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/articles-techniques\\\/rails-6-1-et-ses-nouveautes-notables#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/articles-techniques\\\/rails-6-1-et-ses-nouveautes-notables#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/02\\\/Rails-6.1-et-ses-nouveaute\u0301s-notables.png\",\"datePublished\":\"2021-02-11T23:00:00+00:00\",\"dateModified\":\"2024-08-26T09:31:51+00:00\",\"description\":\"Nos experts pr\u00e9sentent les nouveaut\u00e9s marquantes de Rails 6.1, am\u00e9liorant la gestion des donn\u00e9es et la s\u00e9curit\u00e9.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/articles-techniques\\\/rails-6-1-et-ses-nouveautes-notables#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/ouidou.fr\\\/blog\\\/articles-techniques\\\/rails-6-1-et-ses-nouveautes-notables\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/articles-techniques\\\/rails-6-1-et-ses-nouveautes-notables#primaryimage\",\"url\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/02\\\/Rails-6.1-et-ses-nouveaute\u0301s-notables.png\",\"contentUrl\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/02\\\/Rails-6.1-et-ses-nouveaute\u0301s-notables.png\",\"width\":1105,\"height\":564},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/articles-techniques\\\/rails-6-1-et-ses-nouveautes-notables#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Rails 6.1 et ses nouveaut\u00e9s notables\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/\",\"name\":\"Blog Ouidou\",\"description\":\"Conseil et expertise en technologies\",\"publisher\":{\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/#organization\",\"name\":\"Ouidou\",\"url\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/04\\\/image_2022-04-13_150237378.png\",\"contentUrl\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/04\\\/image_2022-04-13_150237378.png\",\"width\":180,\"height\":180,\"caption\":\"Ouidou\"},\"image\":{\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/ouidou.fr\\\/blog\\\/#\\\/schema\\\/person\\\/e1d66085fb7c22ede319ce56adc373a4\",\"name\":\"Sara Lourties\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/b2ef32f9fc1e16168b39587a2ec1dafedc70a9d41fa1b4a930ec7744b3e35ec7?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/b2ef32f9fc1e16168b39587a2ec1dafedc70a9d41fa1b4a930ec7744b3e35ec7?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/b2ef32f9fc1e16168b39587a2ec1dafedc70a9d41fa1b4a930ec7744b3e35ec7?s=96&d=mm&r=g\",\"caption\":\"Sara Lourties\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Rails 6.1 et ses nouveaut\u00e9s notables - Ouidou","description":"Nos experts pr\u00e9sentent les nouveaut\u00e9s marquantes de Rails 6.1, am\u00e9liorant la gestion des donn\u00e9es et la s\u00e9curit\u00e9.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/ouidou.fr\/blog\/articles-techniques\/rails-6-1-et-ses-nouveautes-notables","og_locale":"fr_FR","og_type":"article","og_title":"Rails 6.1 et ses nouveaut\u00e9s notables - Ouidou","og_description":"Nos experts pr\u00e9sentent les nouveaut\u00e9s marquantes de Rails 6.1, am\u00e9liorant la gestion des donn\u00e9es et la s\u00e9curit\u00e9.","og_url":"https:\/\/ouidou.fr\/blog\/articles-techniques\/rails-6-1-et-ses-nouveautes-notables","og_site_name":"Ouidou","article_published_time":"2021-02-11T23:00:00+00:00","article_modified_time":"2024-08-26T09:31:51+00:00","og_image":[{"width":1105,"height":564,"url":"https:\/\/ouidou.fr\/blog\/wp-content\/uploads\/2021\/02\/Rails-6.1-et-ses-nouveaute\u0301s-notables.png","type":"image\/png"}],"author":"Sara Lourties","twitter_card":"summary_large_image","twitter_misc":{"\u00c9crit par":"Sara Lourties","Dur\u00e9e de lecture estim\u00e9e":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/ouidou.fr\/blog\/articles-techniques\/rails-6-1-et-ses-nouveautes-notables#article","isPartOf":{"@id":"https:\/\/ouidou.fr\/blog\/articles-techniques\/rails-6-1-et-ses-nouveautes-notables"},"author":{"name":"Sara Lourties","@id":"https:\/\/ouidou.fr\/blog\/#\/schema\/person\/e1d66085fb7c22ede319ce56adc373a4"},"headline":"Rails 6.1 et ses nouveaut\u00e9s notables","datePublished":"2021-02-11T23:00:00+00:00","dateModified":"2024-08-26T09:31:51+00:00","mainEntityOfPage":{"@id":"https:\/\/ouidou.fr\/blog\/articles-techniques\/rails-6-1-et-ses-nouveautes-notables"},"wordCount":1901,"publisher":{"@id":"https:\/\/ouidou.fr\/blog\/#organization"},"image":{"@id":"https:\/\/ouidou.fr\/blog\/articles-techniques\/rails-6-1-et-ses-nouveautes-notables#primaryimage"},"thumbnailUrl":"https:\/\/ouidou.fr\/blog\/wp-content\/uploads\/2021\/02\/Rails-6.1-et-ses-nouveaute\u0301s-notables.png","articleSection":["Articles Techniques"],"inLanguage":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/ouidou.fr\/blog\/articles-techniques\/rails-6-1-et-ses-nouveautes-notables","url":"https:\/\/ouidou.fr\/blog\/articles-techniques\/rails-6-1-et-ses-nouveautes-notables","name":"Rails 6.1 et ses nouveaut\u00e9s notables - Ouidou","isPartOf":{"@id":"https:\/\/ouidou.fr\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/ouidou.fr\/blog\/articles-techniques\/rails-6-1-et-ses-nouveautes-notables#primaryimage"},"image":{"@id":"https:\/\/ouidou.fr\/blog\/articles-techniques\/rails-6-1-et-ses-nouveautes-notables#primaryimage"},"thumbnailUrl":"https:\/\/ouidou.fr\/blog\/wp-content\/uploads\/2021\/02\/Rails-6.1-et-ses-nouveaute\u0301s-notables.png","datePublished":"2021-02-11T23:00:00+00:00","dateModified":"2024-08-26T09:31:51+00:00","description":"Nos experts pr\u00e9sentent les nouveaut\u00e9s marquantes de Rails 6.1, am\u00e9liorant la gestion des donn\u00e9es et la s\u00e9curit\u00e9.","breadcrumb":{"@id":"https:\/\/ouidou.fr\/blog\/articles-techniques\/rails-6-1-et-ses-nouveautes-notables#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/ouidou.fr\/blog\/articles-techniques\/rails-6-1-et-ses-nouveautes-notables"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/ouidou.fr\/blog\/articles-techniques\/rails-6-1-et-ses-nouveautes-notables#primaryimage","url":"https:\/\/ouidou.fr\/blog\/wp-content\/uploads\/2021\/02\/Rails-6.1-et-ses-nouveaute\u0301s-notables.png","contentUrl":"https:\/\/ouidou.fr\/blog\/wp-content\/uploads\/2021\/02\/Rails-6.1-et-ses-nouveaute\u0301s-notables.png","width":1105,"height":564},{"@type":"BreadcrumbList","@id":"https:\/\/ouidou.fr\/blog\/articles-techniques\/rails-6-1-et-ses-nouveautes-notables#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/ouidou.fr\/blog\/"},{"@type":"ListItem","position":2,"name":"Rails 6.1 et ses nouveaut\u00e9s notables"}]},{"@type":"WebSite","@id":"https:\/\/ouidou.fr\/blog\/#website","url":"https:\/\/ouidou.fr\/blog\/","name":"Blog Ouidou","description":"Conseil et expertise en technologies","publisher":{"@id":"https:\/\/ouidou.fr\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/ouidou.fr\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/ouidou.fr\/blog\/#organization","name":"Ouidou","url":"https:\/\/ouidou.fr\/blog\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/ouidou.fr\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/ouidou.fr\/blog\/wp-content\/uploads\/2022\/04\/image_2022-04-13_150237378.png","contentUrl":"https:\/\/ouidou.fr\/blog\/wp-content\/uploads\/2022\/04\/image_2022-04-13_150237378.png","width":180,"height":180,"caption":"Ouidou"},"image":{"@id":"https:\/\/ouidou.fr\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/ouidou.fr\/blog\/#\/schema\/person\/e1d66085fb7c22ede319ce56adc373a4","name":"Sara Lourties","image":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/secure.gravatar.com\/avatar\/b2ef32f9fc1e16168b39587a2ec1dafedc70a9d41fa1b4a930ec7744b3e35ec7?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/b2ef32f9fc1e16168b39587a2ec1dafedc70a9d41fa1b4a930ec7744b3e35ec7?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/b2ef32f9fc1e16168b39587a2ec1dafedc70a9d41fa1b4a930ec7744b3e35ec7?s=96&d=mm&r=g","caption":"Sara Lourties"}}]}},"_links":{"self":[{"href":"https:\/\/ouidou.fr\/blog\/wp-json\/wp\/v2\/posts\/7878","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ouidou.fr\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ouidou.fr\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ouidou.fr\/blog\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/ouidou.fr\/blog\/wp-json\/wp\/v2\/comments?post=7878"}],"version-history":[{"count":6,"href":"https:\/\/ouidou.fr\/blog\/wp-json\/wp\/v2\/posts\/7878\/revisions"}],"predecessor-version":[{"id":15982,"href":"https:\/\/ouidou.fr\/blog\/wp-json\/wp\/v2\/posts\/7878\/revisions\/15982"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ouidou.fr\/blog\/wp-json\/wp\/v2\/media\/12518"}],"wp:attachment":[{"href":"https:\/\/ouidou.fr\/blog\/wp-json\/wp\/v2\/media?parent=7878"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ouidou.fr\/blog\/wp-json\/wp\/v2\/categories?post=7878"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ouidou.fr\/blog\/wp-json\/wp\/v2\/tags?post=7878"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}