eclipsephp / world-plugin
Filament plugin for world data
Requires
- php: ^8.2
- bezhansalleh/filament-shield: ^3.3
- datalinx/php-utils: ^2.5
- filament/filament: ^3.3
- spatie/laravel-package-tools: ^1.19
Requires (Dev)
- laravel/pint: ^1.21
- orchestra/testbench: ^10.1
- pestphp/pest: ^3.7
- pestphp/pest-plugin-livewire: ^3.0
Suggests
- tangodev-it/filament-emoji-picker: Show a emoji picker for country flag input
This package is auto-updated.
Last update: 2025-04-10 09:48:34 UTC
README
About
Filament plugin for world data.
✅ Countries
🟧 Geo and special regions (WIP)
🟧 Posts (WIP)
⏳ Other resources coming when needed (suggest a feature and/or hire us)
Requirements
- PHP >= 8.2 (due to Pest 3 requirement)
- Filament 3
- Filament Shield plugin (to manage permissions)
See composer.json for details.
Getting started
- Download it with composer:
composer require eclipsephp/world-plugin
- If you want to use the emoji picker for the country flag, also install the Emoji Picker plugin.
Contributing
Issues
If you have some suggestions how to make this package better, please open an issue or even better, submit a pull request.
Should you want to contribute, please see the development guidelines in the DataLinx PHP package template.
Development
- All development is subject to our PHP package development guidelines.
- Our Filament app development docs will also be helpful.
- Any PRs will generally need to adhere to these before being merged.
Requirements
- Linux, Mac or Windows with WSL
- Lando (optional, but easier to start with)
Get started
- Clone the git repo
- Start the Lando container
lando start
- Install dependencies (this also runs the setup composer script)
lando composer install
- You can now develop and run tests. Happy coding 😉
💡 To manually test the plugin in the browser, see our recommendation, which is also how Filament suggests package development.
However, the plugin should be universal and not dependent on our app setup or core package.
Changelog
All notable changes to this project are automatically documented in the CHANGELOG.md file using the release workflow, based on the release-please GitHub action.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
For all this to work, commit messages must follow the Conventional commits specification, which is also enforced by a Git hook.