Separate endpoints for active vs all categories

[iRahmanG]

Currently, the getAllCategories endpoint returns all categories, including those marked as soft‑deleted (isDelete = true). This can cause confusion because normal users usually expect only active categories, while admins may want to see everything.

Steps to reproduce:

1. Create a new category.
2. Delete it using /delete/{id} (soft delete).
3. Call /getallcategories.
4. The deleted category still appears in the list.

Expected behavior:

• Normal users should only see active categories (isDelete = false).
• Admins should have a way to fetch all categories, including deleted ones.

Suggested improvement:

• Keep /getallcategories for admin use (returns everything).
• Add a new endpoint /categories (or /activecategories) that only returns active categories.
• Repository example for active categories:
  Page<Category> findByIsDeleteFalse(Pageable pageable);
• Service method should use this query for the active categories endpoint.

Why this matters:

• Makes the API behavior clear and predictable.
• Prevents confusion for frontend clients who expect deleted categories to be hidden.
• Still allows admins to audit or restore deleted categories when needed.

[iRahmanG]

I’d like to work on this issue as part of GSSoC 2026

[aryanchoudharyyyy]

I would like to work on this issue under GSSoC 2026.

I understand the problem caused by soft-deleted categories being exposed in the current getAllCategories response. I can implement a separate endpoint for active categories using a filtered query such as findByIsDeleteFalse(Pageable pageable) while keeping the existing endpoint available for admin/audit use cases.

I have experience with Java and Spring Boot APIs, and I’d be happy to work on this enhancement. Please assign this issue to me.

[2024itb047samata]

@rdodiya Kindly assign me this issue.

[iRahmanG]

I closed this issue by mistake.
@rdodiya please reopen it
I would like to work on this issue

[anshika1179]

/assign gssoc