verypossible / atomic_assets Goto Github PK

In lib/rails/generators/atomic_assets/templates/component.rb line 1 references @component.component_name but is never set in the generator.

We should migrate most of the methods out of the templates/component.rb file and push that logic over to the CMS specific generators.

  def edit
    rtn = cms_fields(field_types)
    rtn << h.component(<%= ":#{@component.key}" %>, field_previews).render
    rtn.html_safe
  end

  protected

  def field_previews
    {
      header: "{{preview.header}}",
      content: markdown_preview('preview.content')
    }
  end

  def field_types
    {
      header: { field_type: "text" },
      content: { field_type: "markdown" }
    }
  end

and from the component
if add_option(options[:header])
is an active controller hack that is included in the AtomicCms readme, not even the project.

Lets clean it up!

While installing and configuring the Atomic CMS, at the step where you have to create the text_block component, after I ran rails g atomic_assets:component text_block the terminal hangs.

When creating a new atomic asset, the developer should be able to run

rails g atomic_assets:component component_name 

and have the associated files created for them

• component_name.rb
• component_name.scss
• component_name.js
• component_name.html.slim

Hey guys! :) Tyler asked me to add Spartan as a gem owner on ruby gems. He said the username was "spartansystems", but the CLI wants an email and gives me this result when I try to transfer:

$ gem owner -a spartansytems atomic_assets

# Adding spartansytems: Owner could not be found.

Let me know the email(s) to use, and I will add you guys.