Alan Reid

Thanks for the reply mate, so basically i want to store

{
  "energy_provider": {
      "name": "data",
      "renewal": "data"
  },
  "insurance_provider": {
      "name": "data",
      "renewal": "data"
  }
}

Do you think it would be best to have JSONB fields in the table to store these then? Or do you know of a more efficient way you could suggest please?

I found this article, which seems to be interesting. And maybe worth a look at.

I learnt all about graphQL over at How to GraphQL it's a good resource, and you can select different paths not just Ruby.

You should check out udemy, they have a range of great courses which would cover the topics you want.

As others have said, select a language you want to learn be it Rails or Node.js and work through it. The different languages are just different ways of doing things essentially.

Agreed, this new design is pretty slick Chris! I am also loving tailwind and the whole utility first CSS library.

Once you have made you project, you should run rails db:create to create your database.

It would then do worth looking at The Rail Tutorial which gives a great overview of the basics about Rails. Chapter 2 will give you a good idea on how to deal with migrations, and general DB stuff.

As per this Episode 191 is there any way I can add nested settings? for example:

{
"wants_reminders": true,
"wants_deals_offers": true,
"subscribed_to_newsletter": true,
"something_here": {
    "option1": "data",
    "option2": "data"
}

Let me know how you get on. Hope it goes well.

Of course, it seems to be working well. Saves a load of time. I sure it could be refactored to be quicker too. This was screated from a worker I am using to push updates to shopify - thus the begin, rescue, ensure

class FixProductBodyWorker
  include Sidekiq::Worker
  sidekiq_options retry: false

  def perform()
    batch_index = 1

    Product.where(x: "y")
        .find_in_batches(:batch_size => 100) do | products |

       retries = 3
       begin
         products.each do |product|
          if !product.product_body.nil?

            body_init = product.product_body

            # I added a load of editing stuff here to remove 
                        # unwanted text, or editing parts of the content.

                        # The clear out any whitespace - I do this as a lot 
                        #of the data was scraped from third-party supplier sites.
            body_edit = product.product_body.strip

            product.update(description: body_edit)
          end
         end
       rescue StandardError=>e
         puts "\tError: #{e}"
         if retries > 0
           puts "\tTrying #{retries} more times"
           retries -= 1
           sleep 20
           retry
         else
           puts "\t\tIssues processing batch #{batch_index}, so moving on"
           batch_index += 1
         end
       else
         puts "\tProceesed batch #{batch_index}."
         batch_index += 1
       ensure
         sleep 10
       end
    end
  end
end

Quick update, made a quick worker to take my existing content, and save it to the actiontext table :D Seems to be working a treat!

Now to sit back and wait :D

mmm, wonder if i can create a worker to do it for me basically save from :product_body to :body. I have like 32,000 records to update.

Great video though, i had it up an running in seconds! Then I sat there and went... "Oh, bugger!" hahaha

I followed the great video Chris did on action text, however, I have an existing data structure and want to move it over to use actiontext for editing the body content.

How can i display the old content in the trix editor, if its not been moved over? Is there an easy way?

So how would you set the account_id in the URL when a user logs in? surely its not as simple as just setting Current.account = user.account_id ?

Currently the setup is showing how to use the bash setup, its mainly the oh-my-zsh stuff i'd like to see as im new to that.

I have set it up as much as i can so far haha :)

I have noticed that macOS Catalina moves to ZSH as the default shell, would be cool so get an update on the install rail guide to show this off :)

Thanks Ivan,
A user is a user, they then need an account (for a business) which other users can be assigned to. This is where a user can be a member of an account. I understand the confusion.

later i can add in subscriptions to the mix to expand the app more.

hi Daniel,
yeah a user can be the owner and be assigned to the account.

the updated code seems to work, but im all for finding out better ways to get things done.

Just a quick update, after a little light reading this evening i think this maybe correct. It seems to work ok. If anyone notices something thats wrong please let me know :) thanks.

User.rb

class User < ApplicationRecord
  belongs_to :account
end

Account.rb

class Account < ApplicationRecord
  has_one :owner, class_name: :User, foreign_key: :owner_id
  has_many :users
end

I have a users model, and an accounts model. Basically I would like to have...

• An account has one owner
• An account can have many users
• Users can only be a member of one account.

Does the following look right?

User.rb

class User < ApplicationRecord
  has_many :accounts, foreign_key: :owner_id
end

Account.rb

class Account < ApplicationRecord
  belongs_to :owner, class_name: :User, foreign_key: :owner_id
  has_many :users
end

Seems like a no brainer then haha. No harm in starting a new project and just updating once it goes to stable, I will let you know how I get on.

Hey all,
So i thought i would pose the question and get other users views on Rails 6. So we are still on RC1, its been like this for a while now. I am curious to know others views, and experiences to help me work out if I should start building a new project in Rails 6 (some of the new features would be helpful).

I saw DHH said that its fine to use in production, and that Basecamp and other are using it without issue in its RC state.

Any way let me know
Alan