PHPackages                             jhavenz/nova-extended-fields - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. jhavenz/nova-extended-fields

ActiveLibrary[Utility & Helpers](/categories/utility)

jhavenz/nova-extended-fields
============================

Specific field types for use with Laravel Nova

0.0.6(3y ago)012MITPHPPHP ^8.1

Since Jul 11Pushed 3y ago1 watchersCompare

[ Source](https://github.com/jhavenz/nova-extended-fields)[ Packagist](https://packagist.org/packages/jhavenz/nova-extended-fields)[ Docs](https://github.com/jhavenz/nova-extended-fields)[ RSS](/packages/jhavenz-nova-extended-fields/feed)WikiDiscussions main Synced 3w ago

READMEChangelog (6)Dependencies (10)Versions (7)Used By (0)

### File-based fields for Laravel Nova

[](#file-based-fields-for-laravel-nova)

> Important: This package is still in development/pre-release mode. Please do not use in production yet.

Personally, I'm not a fan of configuring all of my Nova fields within the 'fields' array that Nova expects.

Additionally, most of the fields used across Nova projects tend to have a lot in common...

So isn't there a better way than having to repeat all this logic for each project, plus needing to configure each field with an array and having to (visually) parse through all fields to find the one you're looking for each time? That's what this package aims to fix.

So, instead of something like this in your Nova project:

```