Skip to content

feature_request.md

Latest commit

 

History

History
80 lines (64 loc) · 1.62 KB

feature_request.md

File metadata and controls

80 lines (64 loc) · 1.62 KB
name ✨ Feature Request
about Suggest a new feature or enhancement
title [FEATURE]
labels type: feature, status: needs-triage
assignees

Feature Description

Service Scope

  • Finance Service
  • IAM Service (future)
  • New Service
  • Shared/Common

Problem / Motivation

Proposed Solution

API Design (if applicable)

Proto Definition

// Proposed proto changes
service ExampleService {
  rpc NewMethod(NewMethodRequest) returns (NewMethodResponse);
}

message NewMethodRequest {
  string field1 = 1;
}

message NewMethodResponse {
  string result = 1;
}

REST Endpoint (via gRPC-Gateway)

POST /api/v1/<service>/<resource>
GET  /api/v1/<service>/<resource>/{id}

Database Changes (if applicable)

-- Proposed schema changes
CREATE TABLE new_table (
    id UUID PRIMARY KEY,
    field1 VARCHAR(100) NOT NULL
);

Breaking Changes

  • Yes (describe impact)
  • No

Dependencies

Alternatives Considered

Acceptance Criteria

  • Criteria 1
  • Criteria 2
  • Criteria 3

Additional Context

Checklist

  • I have searched existing issues for duplicates
  • I have read RULES.md
  • This follows Clean Architecture principles
  • Proto changes are backward compatible (or clearly marked as breaking)