Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor Filament resource namespaces for consistency #160

Conversation

sweep-ai[bot]
Copy link
Contributor

@sweep-ai sweep-ai bot commented Jul 20, 2024

Purpose

This pull request aims to refactor the namespace structure of the Filament resources in the liberu-cms/cms-laravel repository. The goal is to ensure consistent naming conventions and organization of the resource files.

Description

The changes made in this pull request include:

  1. Updating the namespace of the TagResource and its related pages from App\Filament\Admin\Resources\TagResource to App\Filament\App\Resources\TagResource.
  2. Updating the namespace of the AuthorResource and its related pages from App\Filament\Admin\Resources\AuthorResource to App\Filament\App\Resources\AuthorResource.
  3. Updating the namespace of the ContentResource and its related pages from App\Filament\Admin\Resources\ContentResource to App\Filament\App\Resources\ContentResource.

These changes ensure that all Filament resources are consistently organized under the App\Filament\App\Resources namespace, which aligns with the overall structure of the application.

Summary

  • Refactored the namespace of TagResource and its related pages to App\Filament\App\Resources\TagResource
  • Refactored the namespace of AuthorResource and its related pages to App\Filament\App\Resources\AuthorResource
  • Refactored the namespace of ContentResource and its related pages to App\Filament\App\Resources\ContentResource

Suggested changes from Sweep Chat by @curtisdelicata. Continue chatting at https://sweep-chat-demo.vercel.app/c/2c432cfd-f851-46f5-990e-556a602f42f9.

@curtisdelicata curtisdelicata merged commit 0a9f74a into main Jul 20, 2024
1 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant