ricvillagrana / easy-record Goto Github PK

Right now we have this way to associate two records:

Assuming that list is a List instance.

Item.new(name: 'Item name', list_id: list.id)

But this way is cleaner and better (UPDATE TO THIS):

Item.new(name: 'Item name', list: list)

Also, would be nice to have this kind of assignments:

list.tasks.append(task)
task.list = list

class Person < EasyRecord
  field :name, String
end

person = Person.new(name: 'John')

# If we want to "clear" the name assigning `nil`, we will ge this error:
# RuntimeError: name cannot receive type `NilClass` because it is defined as `String`
person.name = nil

person.name should be able to get a nil assignment.

Validations are always needed. Currently, datatype is validated but I think it's also great having custom validations.

Example:

class Person < EasyRecord
  field name, String

  # The lambda funciton should return a boolean.
  validate :name, -> (name) { name.size < 50 }
end

Current:

class List < EasyRecord
  field :name, String

  belongs_to :user, { class_name: 'User' }, 'user_id'
  has_many :tasks, class_name: 'Task'
end

New behaviour:

class List < EasyRecord
  field :name, String

  belongs_to :user # it will take class_name `User` and the key `user_id`
  has_many :tasks # it will pluralize and take the `Task` class_name.
end

We need to save our records in json structures.
The files should be places on storage/json/{model_name}.json

1. Is needed for 1:N relationships have a ids method to get an array of ids.
2. Is needed to have a method pluck which take an attribute from the model lists and return an array of the attribute values.

• Add ids method.
• Add pluck method.

Examples

Person.ids # => ['8652b710-cb9f-0137-1165-2cbc32ad1b49', '8652b710-cb9f-0137-1165-2cbc32ad1b50']

Person.pluck :name # => ['John', 'Mike', 'Robin', 'Hannah']

Update readme and add examples directory.

Is needed to have test for this library.
Please use Minitest.

Drop CSV save feature. to only have save method

Fix the code to follow rubocop guides.

Currently I have a method called has_many_simple, but I think that has_many_directly is a better name.

The method is in the associations.rb file.

Feel free to suggest another name if you think is better.

Currently, is needed to have the list_id in the attr_accessor, but would be nice if we can avoid this and only passing the name in the belongs_to.

class List < EasyRecord
  attr_accessor :name

  has_many :tasks, class_name: 'Task'
end

class Task < EasyRecord
  attr_accessor :name, :done, :list_id

  belongs_to :list, { class_name: 'List' }, :list_id
end