tb_core 1.4.beta1 → 1.4.beta2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 7972e913d7dfa93775c49dff5e6bd3fe6bd4781c
-  data.tar.gz: 38b2840a7b5e0770508445c53199de91230c97a9
+  metadata.gz: d3e651f6ff813c429d0d61895739a668b1962417
+  data.tar.gz: 9d4675ce88f2341883c9e07634f8896ff0b871e0
 SHA512:
-  metadata.gz: badde50660d068861e27367ec9033f125e63f53973c5cfa3d496114fabc7675e7ca7b354dd7e6076af254b64517fef074b6a18f5b8e8753379ac0cf70a1d1056
-  data.tar.gz: 82f6a259e226267a08cdf81ee59a8cc57bca8e8a14e7f1f150c57d0e016ac8ad36d567e214bf604fae2b0136e7b59b8edfad98d91486ef277e8ab767be75706a
+  metadata.gz: 7fbe679221366bfeb8aa9050fc32ff06922ee0e394c1c0be637bd9da5cf424d7ea8947e1ba2b075b1c61b3931249f18fad04a60056e435565fe712f9e5a80a3e
+  data.tar.gz: 20240e4966b8ac2446d36629b60a8b01b641493d01bec75b81c5699bae3332c10ea2acce680392049ee19bfb22be712f0d440add299517f9b779b2eb9a277753

data/README.md

@@ -1,3 +1,5 @@
+[![Build Status](https://semaphoreci.com/api/v1/moser-it/tb_core/branches/dev/shields_badge.svg)](https://semaphoreci.com/moser-it/tb_core)
+
 Twice Baked Core
 ================
 
@@ -37,7 +39,7 @@ The `spud:setup` generator takes care of a few tasks for you. If you missed that
 Configuration
 -------------
 
-The core engine provides various configuration options. 
+The core engine provides various configuration options.
 
     Spud::Core.configure do |config|
       config.option = value
@@ -71,7 +73,7 @@ Then, add your module to the `Spud::Core.config.admin_applications` array. We re
       :name => "Clients",
       :thumbnail => "spud/admin/clients.png",
       :url => "/admin/clients",
-      # Optional: 
+      # Optional:
       :badge => ->(user){ Client.where(:is_pending => true).count() }
     }]
 
@@ -96,7 +98,7 @@ Create a file in your app at `app/models/spud_user.rb`, and build a class called
 
 ### Adding fields to the add/edit user form
 
-Create a file in your app at `app/views/admin/users/_form_additions.html.erb`. 
+Create a file in your app at `app/views/admin/users/_form_additions.html.erb`.
 
     <div class="control-group">
       <%= f.label :avatar, :class=>"control-label"%>
@@ -107,7 +109,7 @@ Create a file in your app at `app/views/admin/users/_form_additions.html.erb`.
 
 ### Adding fields to the user show action
 
-Create a file in your app at `app/views/admin/users/_show_additions.html.erb`. 
+Create a file in your app at `app/views/admin/users/_show_additions.html.erb`.
 
     <% if @user.avatar_file_name %>
       <dt>Avatar</dt>
@@ -204,8 +206,8 @@ Checking permissions is easy. Each permission has a `tag` which is a unique, nam
 
 Permissions are created one of two ways:
 
-1. Every dashboard app automatically generates a "Full Access" permission, with a tag of `admin.(app name).full_access`. 
-2. You as the developer may append custom permissions to the `Spud::Core.permissions` array. 
+1. Every dashboard app automatically generates a "Full Access" permission, with a tag of `admin.(app name).full_access`.
+2. You as the developer may append custom permissions to the `Spud::Core.permissions` array.
 
 Create custom permissions whenever you need to permit an action that falls outside of the standard "full access to an app" use case; For example, turning on/off the ability for a user to upload an avatar.
 
@@ -218,7 +220,7 @@ Create custom permissions whenever you need to permit an action that falls outsi
       <%= link_to 'Upload Avatar', upload_avatar_path %>
     <% end %>
 
-Finally, custom permissions may optionally be tied to one or more dashboard apps. A user who has the permission shown below would have access to the the Clients and Projects dashboard apps. After that is is up to you to code your view and controller logic in accorance to what permissions the user has. 
+Finally, custom permissions may optionally be tied to one or more dashboard apps. A user who has the permission shown below would have access to the the Clients and Projects dashboard apps. After that is is up to you to code your view and controller logic in accorance to what permissions the user has.
 
     // application.rb
     Spud::Core.permissions += [{
@@ -233,7 +235,7 @@ Testing
 Twice Baked uses RSpec for testing. Get the tests running with a few short commands:
 
 1. Create and migrate the databases:
-   
+
         rake db:create
         rake db:migrate
 

data/app/assets/javascripts/tb_core/remote.js

@@ -99,10 +99,10 @@ var onRemoteFormErrors = function(event, jqXHR, textStatus, errorThrown){
   var errorType = $form.data('errors');
   if(jqXHR.status == 422){
     if(errorType == 'inline'){
-      displayErrorsInline($form, jqXHR.responseJSON);
+      tb.remote.displayErrorsInline($form, jqXHR.responseJSON);
     }
     else{
-      displayErrorsAlert(jqXHR.responseJSON);
+      tb.remote.displayErrorsAlert(jqXHR.responseJSON);
     }
   }
   else if(jqXHR.status == 401 || jqXHR.status == 403){
@@ -116,7 +116,7 @@ var onRemoteFormErrors = function(event, jqXHR, textStatus, errorThrown){
 /*
 * Append error text to form input fields and scroll to the first error
 */
-var displayErrorsInline = function($form, errors){
+tb.remote.displayErrorsInline = function($form, errors){
   $form.find('.form-error-inline, .form-error-base').remove();
   for(var key in errors){
     var messages = errors[key].messages;
@@ -166,7 +166,7 @@ var displayErrorsInline = function($form, errors){
 /*
 * Display errors in a standard window.alert dialog
 */
-var displayErrorsAlert = function(errors){
+tb.remote.displayErrorsAlert = function(errors){
   var text = "Please correct the following errors:\n";
   var label, message;
   var index = 0;

data/lib/generators/spud/module_generator.rb

@@ -64,8 +64,12 @@ EOF
 
   def create_specs
     string_attribute = find_first_string_attr()
-    Rails::Generators.invoke 'spud:controller_spec', ["#{module_name}", string_attribute, 0], behavior: behavior
-    Rails::Generators.invoke 'spud:controller_spec', ["Admin/#{module_name}", string_attribute, 1], behavior: behavior
+    Rails::Generators.invoke 'spud:controller_spec',
+      ["#{module_name_formatted}", string_attribute, 0],
+      behavior: behavior
+    Rails::Generators.invoke 'spud:controller_spec',
+      ["Admin/#{module_name_formatted}", string_attribute, 1],
+      behavior: behavior
   end
 
   def field_for_attribute(type, name)

data/lib/spud_core/engine.rb

@@ -17,6 +17,7 @@ module Spud
     class Engine < ::Rails::Engine
       require "#{root}/lib/spud_core/errors"
       require "#{root}/lib/spud_core/searchable"
+      require "#{root}/lib/tb_core/form_builder"
 
       engine_name :tb_core
       config.autoload_paths << "#{root}/lib"

data/lib/spud_core/version.rb

@@ -1,5 +1,5 @@
 module Spud
   module Core
-    VERSION = '1.4.beta1'
+    VERSION = '1.4.beta2'
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: tb_core
 version: !ruby/object:Gem::Version
-  version: 1.4.beta1
+  version: 1.4.beta2
 platform: ruby
 authors:
 - Greg Woods
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-09-09 00:00:00.000000000 Z
+date: 2016-09-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
@@ -140,16 +140,16 @@ dependencies:
   name: bootstrap-sass
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - "<"
       - !ruby/object:Gem::Version
-        version: 3.3.7
+        version: '4.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - "<"
       - !ruby/object:Gem::Version
-        version: 3.3.7
+        version: '4.0'
 - !ruby/object:Gem::Dependency
   name: sass-rails
   requirement: !ruby/object:Gem::Requirement