update component generator according to jonas' feedback

Author: pascalwengerter

lib/generators/matestack_component/USAGE

@@ -1,8 +1,11 @@
 Description:
-    Explain the generator
+    Generates matestack components to app/matestack/components
 
 Example:
-    rails generate matestack_component Thing
+    rails generate matestack_component NAME --(no-)dynamic --(no-)haml --(no-)scss
 
     This will create:
-        what/will/it/create
+        app/matestack/components/NAME.rb
+        (app/matestack/components/NAME.js if --dynamic)
+        (app/matestack/components/NAME.haml if --haml)
+        (app/matestack/components/NAME.scss if --scss)

lib/generators/matestack_component/matestack_component_generator.rb

@@ -2,22 +2,26 @@ class MatestackComponentGenerator < Rails::Generators::NamedBase
   source_root File.expand_path('templates', __dir__)
 
   class_option :dynamic, type: :boolean, default: false
+  class_option :scss, type: :boolean, default: false
+  class_option :haml, type: :boolean, default: false
   class_option :namespace, type: :string
 
   def create_matestack_component
     @dynamic = options[:dynamic]
     @namespace = options[:namespace]
 
-    to_be_created_files = ['.rb', '.haml', '.scss']
-    to_be_created_files << '.js' if @dynamic == true
+    # Future: Check for matestack-compatible namespacing!
+
+    to_be_created_files = ['.rb']
+    to_be_created_files << '.js' if options[:dynamic]
+    to_be_created_files << '.scss' if options[:scss]
+    to_be_created_files << '.haml' if options[:haml]
 
     matestack_component_dir_path = "app/matestack/components/"
     matestack_component_dir_path << "#{@namespace}/" unless @namespace.nil?
-#    matestack_component_dir_path << "#{file_name}"
 
     to_be_created_files.each do |file|
       generator_path = matestack_component_dir_path + "/#{file_name}#{file}"
-
       template "matestack_component#{file}.erb", generator_path
     end
 

lib/generators/matestack_component/templates/matestack_component.js.erb

@@ -1,30 +1,12 @@
-// this component is way overblown. Make sure to delete everything you don't need, mate!
-
-import Vue from 'vue/dist/vue.esm'
-import Vuex from 'vuex'
-import axios from 'axios'
-
-import matestackEventHub from 'core/js/event-hub'
-
-import componentMixin from 'component/js/component'
-
-const componentDef = {
-  mixins: [componentMixin],
-  data: function(){
+MatestackUiCore.Vue.component('custom<% unless @namespace.nil? %>-<%= @namespace %><% end %>-<%= file_name %>', {
+  mixins: [MatestackUiCore.componentMixin],
+  data() {
     return {
-      data: {},
-      errors: {}
-    }
+      data: []
+    };
   },
   methods: {},
-  created: function () {},
-  beforeDestroy: function() {},
   mounted: function(){
     console.log('Custom Dynamic Component <%= class_name %> mounted!')
   }
-}
-
-MatestackUiCore.Vue.component('custom-<%= file_name %>', { ... }); //no -cell postfix
-let component = Vue.component('<%= file_name %>-cell', componentDef)
-
-export default componentDef
+});

lib/generators/matestack_component/templates/matestack_component.rb.erb

@@ -1,28 +1,12 @@
-class Components::<% unless @namespace.nil? %><%= @namespace.camelize %>::<% end %><%= class_name %>::Cell::<%= class_name %> < Matestack::Ui::<% if @dynamic == true %>DynamicComponent<% else %>StaticComponent<% end %>
-
-  REQUIRED_KEYS = [] # [:symbols]
-
-  # use the setup method if dealing with a dynamic component and/or to use custom HAML files
-  def setup
-    # access the Vue.JS component_config
-    # @component_config[:attribute] = attribute
-    # set up tag_attributes to use in the HAML view
-    # @tag_attributes.merge!({ "attribute": options[:attribute],
-    #   "href": link_path,
-    #   "@click.prevent": navigate_to(link_path),
-    #   "v-bind:class": "{ active: isActive }",
-    #   "target": options[:target] ||= nil
-    # })
-  end
+class Components::<% unless @namespace.nil? %><%= @namespace.camelize %>::<% end %><%= class_name %> < Matestack::Ui::<% if @dynamic == true %>DynamicComponent<% else %>StaticComponent<% end %>
 
   def prepare
     # DB queries and API calls go here
   end
 
-  # use the response method if you only need to orchestrate existing matestack components
   def response
     components {
-      # other matestack components go here
+      # orchestrate existing matestack components here
     }
   end