Download the PHP package laraning/nova-time-field without Composer
On this page you can find all versions of the php package laraning/nova-time-field. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package nova-time-field
A time field for Laravel Nova applications
This package contains a Nova field to allow you to store time values. Under the hood it uses the flatpickr default Laravel Nova Calendar library.
Installation
You can install this package in your Laravel Nova app via composer:
Usage
You can use the Laraning\NovaTimeField\TimeField namespace in your Nova resource:
By default the time component uses a 24 hour format. Still you can make it in 12h format like:
You can also change the default 5 minute increments to another number:
You can make sure that all times entered are converted back to your base app timezone (set in config/app.php) by calling
the withTimezoneAdjustments() method on your field.
An example of this would be when your app is set to GMT but your user is in BST (GMT+1). The user would still be able to interact with the timefield in their local time, but the time would be saved into the database in GMT.
E.G. The user may select 14:00. They will always see the time as 14:00, but the database will save it as 13:00 as it makes the BST -> GMT adjustments behind the scenes.
As well as handling switching the time to and from your base app timezone, you may also pass in a timezone offset (in minutes),
such as the one returned by moment().utcOffset(). This will then adjust the time to display with the adjusted timezone
rather than the users timezone. This is useful if you're saving the time in UTC along with the offset of the browser that
was used to submit it.
Here you can see how we'd move UTC to BST by passing an offset of 60
Current development status
- [x] Make release 0.1.0.
- [ ] Add minimal test scenarios.
- [x] Add timezone support.
Changelog
Please see CHANGELOG for more information on what has changed recently.
License
The MIT License (MIT). Please see License File for more information.
