It is just a different way to parse the JSON. If you wanted to reference the object, you could do it with something like `version.object['first_name']` but I think that something like `version.changed_object.first_name` appears nicer. It is really just a preference.

You can check the docs for additional tags https://docs.gitlab.com/ce/ci/yaml/README.html#validate-the-gitlab-ciyml Which also includes a validator at /ci/lint. Alternatively, you can make a post request to the ApI https://docs.gitlab.com/ee/api/lint.html

You could try to change the controller endpoint so it's not going to devise, but rather a user controller. So you wouldn't use the `edit_user_registration_path` in the view, but rather something like edit_user. With Devise, you may need to add something like `bypass_sign_in(current_user)` as it will sometimes log a user out on changes. So the edit action of the UsersController may look like this. ``` def update if current_user.update_attributes(user_params) bypass_sign_in(current_user) if params[:user][:avatar].present? render :crop else redirect_to edit_user_path(current_user), notice: "Successfully updated user." end else render :edit end end ```

I've had a chance to look at this gem. Its documentation is pretty extensive which is always nice to see. I'll consider covering this gem in the future. One thing that I highly dislike about this gem is that it seems a lot more invasive in the models. It also has a lot of added complexity based on the documentation and I'm not convinced that it's necessary to accomplish what they're doing. Overall the gem does look pretty cool and for a large complex app, this may be a good fit.

Yea, I could do a video or blog post on how I set up my editor. It's overall fairly simple, but I do have some things that I do normally that others may not.