Laravel API开发：如何通过分类ID关联获取对应文章

Got it, let's walk through how to optimize this API to use category IDs instead of names—this is a great move for maintainability, since category names can change without breaking your code. Here's a step-by-step solution tailored to Laravel:

1. Ensure Your Database Has the Right Relationship Setup #

First, your posts table needs a category_id foreign key that links to the id column of your categories table. If you don't have this column yet, create a migration to add it:

// Create a new migration with: php artisan make:migration add_category_id_to_posts_table
use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;

return new class extends Migration {
    public function up() {
        Schema::table('posts', function (Blueprint $table) {
            $table->unsignedBigInteger('category_id')->nullable();
            // Add foreign key constraint to enforce referential integrity
            $table->foreign('category_id')
                  ->references('id')
                  ->on('categories')
                  ->onDelete('set null'); // Set to null if category is deleted
        });
    }

    public function down() {
        Schema::table('posts', function (Blueprint $table) {
            $table->dropForeign(['category_id']);
            $table->dropColumn('category_id');
        });
    }
};

Run the migration with php artisan migrate to apply the changes.

2. Define Model Relationships #

Set up the Eloquent relationships between your Post and Category models to make querying cleaner:

Post Model (app/Models/Post.php) #

namespace App\Models;

use Illuminate\Database\Eloquent\Model;

class Post extends Model {
    // Define the inverse relationship: A post belongs to one category
    public function category() {
        return $this->belongsTo(Category::class);
    }
}

Category Model (app/Models/Category.php) #

namespace App\Models;

use Illuminate\Database\Eloquent\Model;

class Category extends Model {
    // Define the relationship: A category has many posts
    public function posts() {
        return $this->hasMany(Post::class);
    }
}

3. Update the Controller Method #

Now modify your getPostsByCategory method to accept a category_id parameter, validate it, and fetch posts using the ID. We'll add validation to ensure the ID exists in the categories table:

// app/Http/Controllers/PostController.php
namespace App\Http\Controllers;

use App\Models\Category;
use Illuminate\Http\Request;

class PostController extends Controller {
    public function getPostsByCategory(Request $request) {
        // Validate incoming request data
        $validated = $request->validate([
            'category_id' => 'required|integer|exists:categories,id'
        ]);

        // Option 1: Fetch via Category model (great if you need category data too)
        $category = Category::with('posts')->findOrFail($validated['category_id']);
        $posts = $category->posts;

        // Option 2: Direct query on Post model (simpler if you only need posts)
        // $posts = \App\Models\Post::where('category_id', $validated['category_id'])->get();

        return response()->json(['posts' => $posts]);
    }
}

4. Adjust Your API Usage #

Update any frontend or client that calls this API to send a category_id parameter instead of category. For example, instead of ?category=tech, send ?category_id=1.

Bonus: Use RESTful Routing (Optional) #

For a more RESTful approach, you can define your route to accept the category ID as a URL parameter instead of a query string:

// routes/api.php
use App\Http\Controllers\PostController;

Route::get('/categories/{category}/posts', [PostController::class, 'getPostsByCategory']);

Then adjust the controller method to accept the Category model via route model binding (Laravel will automatically fetch the category or throw a 404):

public function getPostsByCategory(Category $category) {
    $posts = $category->posts;
    return response()->json(['posts' => $posts]);
}

This way, your API URL would look like /api/categories/1/posts—cleaner and more aligned with REST conventions.

内容的提问来源于stack exchange，提问作者Pranav Mandlik