juspay/hyperswitch

refactor(opensearch): Add trait based inputs for opensearch query builder

Open

#5,222 opened on Jul 5, 2024

View on GitHub
 (1 comment) (0 reactions) (1 assignee)Rust (42,690 stars) (4,676 forks)batch import
A-AnalyticsC-refactorgood first issue

Description

Add trait based inputs for opensearch query builder

Currently, we are taking string as input to the filter clause, but we need to use a trait which can take in any generic type as input to the filter clause.

Contributor guide

Tech stack
rust
Domain
backendsearch
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
understanding of Rust traitsfamiliarity with OpenSearch query builder
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue is assigned to someone (assigneesCount: 1). The goal is to introduce a trait to replace the current String input for the filter clause in the OpenSearch query builder. To contribute, review the existing filter clause implementation in the codebase, understand how generics and traits are used in similar places, and potentially collaborate with the assignee. Look at existing trait definitions for inputs in the OpenSearch module. The change is localized to the filter clause interface.
refactor(opensearch): Add trait based inputs for opensearch query builder · juspay/hyperswitch#5222 | Good First Issue