draper | Decorators/View-Models for Rails Applications

just put translated_coordinates and print(translated_coordinates) out of the loop:

Draper infers the decorator from the object that is decorated and in your scenario is Employers::Job.

Because the decorator you want to be used has a totally different name, Api::V2::Employers::JobDecorator, you need to explicitly specify it.

So, Api::V2::Employers::JobDecorator.decorate(@job) is what you need.

More information, here

Several problems:

• \citep is a natbib macro. If you want to use it in biblatex, you must use the natbib option when you load biblatex.

• you shouldn't load package more then once. You MUSTN'T load them more than once with different options. An error message will explicitly tell you about the option clash for the geometry package

• the syntax \begin{filecontents*}[overwrite]{\references.bib} is wrong, references.bib should just be the filename, not a (non-existent) macro

• the note field in the wikipedia entry caused come probelems, so I moved it to another field.

This decorator inherits from Draper::Decorator and object is a method defined on Draper::Decorator. Quote from the docs:

#object ⇒ Object (readonly)

Also known as: model

Returns the object being decorated.

It returns the object that was passed to as the first argument to the decorator's initialize.

That ArgumentError is raised because you call birthday without passing in a date.
Doing <%= user.decorate.birthday(Date.current) %> will make the error go away.

But, this is probably not what you want since date is defined in the User model.

The easiest way to decorate something is to use delegate_all. It will make all methods from the User model available in the decorator.

The key to your issue is the second line of your backtrace, in which you can see that the draper gem is intercepting unknown messages.

That particular method is looking out for specific calls, and if it doesn't need to act upon the message it's intercepting, it attempts to direct them back to the main application.

Unfortunately, the manner in which it's doing so isn't compatible with your version of Ruby, which I suspect is version 3. Ruby's internal handling of method arguments changed between versions 2.x and 3.x, and the released version of Draper relied upon the 2.x implementation.

This issue in the Draper repo matches what you're seeing in your code base.

Until a formal fix is released, you can update your Gemfile to point directly to the Draper repo rather than the cut gem version:

I'm not really sure what happened and why but I tried doing this on my rails container and I was no longer receiving the said error.

1. docker-compose run --rm bash
2. cd to project directory
3. bundle install

You can try the builder pattern. I am not familiar with a ruby gem, but you can find information here: https://en.wikipedia.org/wiki/Builder_pattern and https://en.wikipedia.org/wiki/Fluent_interface

How I solved it:

1. Go to server command line
2. As we can see in error log, the last command before error appears was:

Command: cd /home/deploy/project/releases/20201018151933 && ( export RAILS_ENV="production" RBENV_ROOT="$HOME/.rbenv" RBENV_VERSION="2.6.5" ; RBENV_ROOT=$HOME/.rbenv RBENV_VERSION=2.6.5 $HOME/.rbenv/shims/bundle exec bundle check )

So we go to our folder:

cd /home/deploy/project/releases/20201018151933

and run there command:

export RAILS_ENV="production" RBENV_ROOT="$HOME/.rbenv" RBENV_VERSION="2.6.5" ; RBENV_ROOT=$HOME/.rbenv RBENV_VERSION=2.6.5 $HOME/.rbenv/shims/bundle exec bundle check

After that we see same error:

Could not find concurrent-ruby-1.1.7 in any of the sources. Run 'bundle install' to install missing gems.

1. In same folder run bundle install and after gem installed we can out of server command line.
2. Run cap production deploy and everything is gonna be fine.

I still don't know what is the root problem of this error, and how to fix it permanently, but this works for me. I hope it will be useful for anyone else.