markmercedes / krudmin Goto Github PK

• DateTime field
• Email Field
• Belongs to Link for relations in show page
• Layout API
• Spanish Translations
• Stand Alone controllers that don't depend on having a resource manager but are able to display content using the app template
• Generators
• Code Documentation
• Wiki
• Publish Gem
• Deploy Sample App
• Promote project in ruby toolbox, etc..

• This way, if the user choses to, the show view will be able to display fields grouped by their logical context.

• Buttons will have internal logic and they will decide wether or not they are displayable based on their context and policy permissions for the given resource

class AddButton < Button::Base
  def initialize(policy, action_path)
    @policy, @action_path = policy, action_path
  end

  def to_s
    = link_to(new_resource_path, class: 'btn btn-success') do
      %i.fa.fa-plus
      = t('krudmin.actions.add_new')
  end

  def render
    to_s if policy.new?
  end
end

AddButton.for(policy, new_resource_path)

create corresponding view helpers for buttons, this will prevent the need of invoking full names for button classes inside the views

= Krudmin::ActionButtons::AddButton.new(self, new_resource_path)

= add_button(self, new_resource_path)

• Field
• Action Buttons
• Theme
• Controller
• Resource Manager
• Managed Resource (Controller + Resource Manager + Specs)
• Policy

#32

#89

Ex.

After adding a new controller inheriting Krudmin:CustomController and no views created yet,
the following error is shown, instead of a more guiding error about the resource missing:

And it is actually misleading because Krudmin:CustomController is not supposed to be controlled by a ResourceManager, yet the error says is looking for one.

Constant that contains the presentation logic:

PRESENTATION_METADATA

Concept:

PRESENTATION_METADATA = {
  general: { label: "General", class: 'col-lg-4 col-md-6 col-sm-12', partial_form: "/admin/custom_partial"},
}

This kind of controllers will consume data from a given resource manager and will provide read only access for the data wrapped inside of the resource.

Date fields not returning default value. Fixed on #11

Add a DISPLAY_ATTRIBUTES to the resource manager in order to control which fields appear in the show page.

• Add partial view that will render form errors for cases where submit is not successful.
• Populate error info for fields marked as erroneous, add validations compatibles with rails client-side validations.

Currently , you have to specify the attributes in the EDITABLE_ATTRIBUTES and LISTABLE_ATTRIBUTES

Given that i want to search for an entity's id property, the framework currently removes the id from the field name, i want to be able to explicitly say entity id on the search panel.

as an example see the lister field on the bottom right of the following image

a possible DSL could be
SEARCHABLE_ATTRIBUTES = [:title, :id, :source, :expires_on, :category_id, :area_id, :lister_first_name, :lister_last_name, lister_id: "Lister ID"]

or maybe even pass down options

SEARCHABLE_ATTRIBUTES = [:title, :id, :source, :expires_on, :category_id, :area_id, :lister_first_name, :lister_last_name, lister_id: {label: 'Lister ID'}]

• Move pundit inclusion to sample app, the basic gem only should provide an adapter in order to work with pundit.
• The needed logic about the pundit integration belongs in the sample app, the client app is the one that also should install the pundit gem.
• Create documentation page explaining how to use pundit as the authorization library.

Add a flag for Krudmin:Fields:HasMany that does not allow the _destroy attribute and no delete button is render on the _has_many_fields partial.

e.g:

{format: this.data('date-format')}

  $('.datetimepicker').daterangepicker(
    $.extend({
      timePicker: true,
      locale: {
        format: "MM/DD/YYYY hh:mm A"
      }
    }, inputDefaults)
  , function(inputValue) {
    this.element.val(inputValue.format("MM/DD/YYYY hh:mm A"));
  });

  $('.datepicker').daterangepicker(
    $.extend({
      locale: {
        format: "MM/DD/YYYY"
      }
    }, inputDefaults),
    function(inputValue) {
      this.element.val(inputValue.format("MM/DD/YYYY"));
    }
  );

Current implementation render default rails controls for date and datetime fields.

Allows to configure the theme used, by default the theme under the application will be used, a configuration option should be provided in order to change the default theme.

Organize theme files under logical theme structure

• Image Type
• Regex Support
• ActiveStorage

Add renderers for each field type and allow to specify a custom renderer for a specific field from the resource manager.

#30