bgaze / bootstrap-form Goto Github PK
View Code? Open in Web Editor NEWBootstrap 4 forms builder for Laravel 5.8+
Home Page: https://packages.bgaze.fr/bootstrap-form
License: MIT License
Bootstrap 4 forms builder for Laravel 5.8+
Home Page: https://packages.bgaze.fr/bootstrap-form
License: MIT License
@checkbox('recently_sold','Include recently sold listings',1,true,['switch'=>true])
Not sure why but when It try to check a checkbox by default, it doesn't have that state. Am I doing something wrong?
I'm unable to render view through blade directive where BF facade is working.
brackets are missing for BF::close, it should be BF::close() in documentation otherwise this would throw an exception (Undefined class constant 'close'
).
Liking this package so far.
Any way to add custom-select
to a @select
?
It should probably be the default tbh.
https://packages.bgaze.fr/bootstrap-form
In the publish command it missing "
As the title states, it seems like you accidentally left some test data in the code, so Form Groups are gaining a class of "test". It shouldn't affect anything unless someone has a custom class with that name, but it's still probably something you don't want there. This can even be seen in the examples in the documentation.
This is bordering on being a feature request, but it seems like file inputs remaining as the html standard while every other input has a form-control class makes the file input look out of place, while giving it a form-control class gives it the same shape and size as the rest of the inputs.
Without form-control:
With form-control:
I couldn't tell if this was intentional, but every other input creates a Name and an ID attribute when you give a name argument, but @hidden only creates the name attribute.
Is there a way config an error bag for a form?
Hello,
first: thank you for this useful library! It really simplifies things.
I have an issue with using model binding with store and update. This is how I open the form:
/*[...]*/
@open(['model' => $news, 'update' => 'Backend\NewsController@update', 'store' => 'Backend\NewsController@store'])
/*[...]*/
Now if I try to save a new record I get the following error:
Symfony\Component\HttpKernel\Exception\MethodNotAllowedHttpException thrown with message "The POST method is not supported for this route. Supported methods: GET, HEAD, PUT, PATCH, DELETE."
this is the definition for this route:
Route::group(['prefix' => 'backend', 'as' => 'backend.', 'namespace' => 'Backend'], function() {
/* [...] */
Route::group(['as' => 'contents.'], function() {
Route::resource('news', 'NewsController');
});
});
Updating an existing record works. Am I missing something? I'm using Laravel 6.5.0.
Edit: I can create new records when I use a different form @open(['action' => 'Backend\NewsController@store'])
, but I'd like to use the update-/store-option so I can use the same template for both actions.
Setting any radio input to required should set the whole group to be required, but when I add 'required' to the options on a radio group, it doesn't have any effect. Ideally, adding ['required' => true] to a radio input group would set the first option to required.
Hello,
Since the third Alpha version of Bootstrap 5 will be out soon, it would be great if support could be added to this package. In my opinion, this package offers the best combination with regards to forms in Laravel and Bootstrap. I am sadly not too familiar with the inner workings of the package, else I would have created a proposal.
The changelog is not that huge regarding forms (https://v5.getbootstrap.com/docs/5.0/migration/):
I am not sure if it's best to support two versions of the package or to add a config variable to switch between v4 and v5. Since the forms are rather similar, it might be easiest to add a config variable.
Something in release 1.0.4 broke the labels of checkbox and radio choices. They are all inheriting the group name, so if a radio group is named "Colors", all radio choices will be labeled "Colors" as well.
By default, feedback is not visible in Bootstrap 4. Feedback becomes visible when adjacent to an element with the class 'is-invalid'. This works for normal inputs, but input groups have a parent div which prevents the feedback from showing up.
The Bootstrap documentation avoids this issue by appending the feedback to the input instead of the form-group, keeping the feedback inside the input-group. Perhaps this functionality could be added to the feedback for input-group elements.
Is there or could there be a way to automatically add a class to all labels, except functional labels for checkboxes/radios? It would be nice to add the 'form-label' class to all form group labels, instead of having to specify the label and its class for each input.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.