forxer / blade-ui-kit-bootstrap Goto Github PK

I am embarrassed for this form field because to apply Bootstrap styles there are 3 elements with dedicated classes:

<div class="form-check">
    <input class="form-check-input" type="checkbox" value="" id="flexCheckDefault">
    <label class="form-check-label" for="flexCheckDefault">
         Default checkbox
    </label>
</div>

So I can't just extend the Blade UI Kit Checkbox component.

I think I'm going to have to create components specific to this package. But we are going to lose granularity.

Description:
I encountered an error while using the x-hidden input.
Laravel is returning the following error message: "View [bootstrap-4.components.forms.inputs.hidden] not found".
It seems that Laravel is unable to locate the specified view.

Steps to reproduce:

Add the x-hidden element.
Observe the error message displayed.

Error message :
View [bootstrap-4.components.forms.inputs.hidden] not found.

Additional information:

Laravel version: 10.13.5
Relevant code snippets or configurations:

Please let me know if there is any further information needed.

This component should be fairly simple to implement.

I'm worried, I may have been wrong about the future of the basic package: Blade UI Kit.

I was sure this was the way to go because "powered" by a member of the Laravel team. But while digging I realize that there is a form of uncertainty about the future of this basic package.

The original author launched a call for co-contributors in November 2021. The decision was made to add two trustworthy and proven people. And the request has been closed.

What worries me is that it doesn't seem to have changed things, the project is stagnating on the same date. I'm not criticizing anyone, it's open source, I see.

But suddenly I wonder if this package should not emancipate from its parent.

There are a few components that I don't find relevant in the Blade UI Kit or that will never cover the majority of use cases.

There are other packages that already exist but which, in my view, go too far in abstraction.

For me a component should be a way to write less code to do more.

My growing idea as I write these words is that this package will separate from its illustrious parent.

By getting rid of Blade UI Kit, this would simplify things on several issues that are currently being circumvented. I am thinking, for example, of the management of "online errors".

Following #8 the decision is made that this package "break away" from Blade UI Kit in order to follow our own path.

Besides the changes in the code which are not huge. On the other hand, this implies reviewing ALL the documentation... :/

We need to find a way not to have to add the :errors="$errors" attribute but to manage it internally in the component classes.

Develop a "Modal" component.

Something stylish:

  <button type="button" class="btn btn-primary" data-bs-toggle="modal" data-bs-target="#modal-example">
    Open modal
  </button>

  <x-modal id="modal-example" title="Modal title">
    {{ $slot }}
    <x-slot name="footer">
      <button type="button" class="btn btn-primary">Save</button>
      <button type="button" class="btn btn-secondary" data-bs-dismiss="modal">Dismiss</button>
    </x-slot>
  </x-modal>

As on Blade UI Kit this package will need its own blade directives for styles and scripts.