Skip to content

[FEATURE]: Implement Advanced Search, Category Filtering, and Sorting on Explorer Page #54

Description

@hrshjswniii

Feature and its Use Cases

What is the feature?

Enhance the current Oracle Explorer page (app/explorer/page.tsx) by upgrading the simple text search bar into a full-featured filter and search toolbar. This includes:

  1. Multi-Field Search: Expand search to match oracle names, descriptions, contract addresses (0x...), and token addresses.
  2. Category & Status Filtering: Dropdown selectors to filter oracles by Category (Price Feed, TWAP, Governance / Custom) and Status (Active, Maintenance, Inactive).
  3. Sorting Options: Dropdown control to sort oracles by:
    • Last Submission Time (Newest / Oldest)
    • Name (Alphabetical A–Z / Z–A)
  4. Active Filters Bar & Quick Reset: Visual chips showing active filters with a one-click "Clear All Filters" button.

How would users benefit from it?

  • Efficient Feed Discovery: Users and DApp developers can instantly find specific price feeds or contract instances without manually scrolling through a long grid of cards.
  • Better UX & Scalability: As the number of deployed base and composed oracles on the network grows, advanced sorting and filtering ensure the interface remains fast, responsive, and easy to navigate.
  • Direct Address Lookup: Enables Web3 developers to directly search by contract address (0x...) to quickly locate and verify their deployed oracle instances.

Additional Context

  • Relevant File: [app/explorer/page.tsx] & [hooks/useOracles.ts]
  • Current Limitation: In ExplorerPage, filteredOracles currently only filters oracle.name and oracle.description using a simple string .includes() match, and hardcodes oracle.status === "active".
  • Proposed Technical Approach:
    • Utilize shadcn/ui <Select> and <Badge> components for consistent UI styling matching the existing theme system.
    • Wrap filter and sort parameters in a single combined useMemo block in ExplorerPage to maintain fast client-side rendering performance.
    • Implement fallback skeleton grid loaders when filter options change state.

Code of Conduct

  • I have joined the Discord server and will post updates there
  • I have searched existing issues to avoid duplicates

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions