chore: kickMemberV2Inner

src/core/apis/group.ts

@@ -7,6 +7,8 @@ import {
     GroupNotify,
     GroupRequestOperateTypes,
     InstanceContext,
+    KickMemberInfo,
+    kickMemberV2Req,
     MemberExtSourceType,
     NapCatCore,
     NodeIKernelGroupListener,
@@ -219,6 +221,9 @@ export class NTQQGroupApi {
         // GetMsgByShoretID(ShoretID); -> MsgService.getMsgs(Peer,MsgId,1,false); -> 组出参数
         return this.context.session.getGroupService().addGroupEssence(param);
     }
+    async kickMemberV2Inner(param: kickMemberV2Req) {
+        return this.context.session.getGroupService().kickMemberV2(param);
+    }
     async quitGroupV2(GroupCode: string, needDeleteLocalMsg: boolean) {
         let param = {
             groupCode: GroupCode,

src/core/entities/group.ts

@@ -1,5 +1,17 @@
 import { QQLevel, Sex, User } from './user';
-
+export interface KickMemberInfo {
+    optFlag: number,
+    optOperate: number,
+    optMemberUid: string,
+    optBytesMsg: string,
+}
+export interface  kickMemberV2Req{
+    groupCode: string,
+    kickFlag: number,
+    kickList: Array<KickMemberInfo>,
+    kickListUids: Array<string>,
+    kickMsg: string
+}
 export enum GroupListUpdateType {
     REFRESHALL,
     GETALL,

src/core/services/NodeIKernelGroupService.ts

@@ -5,14 +5,16 @@ import {
     GroupMemberRole,
     GroupNotifyMsgType,
     GroupRequestOperateTypes,
+    kickMemberV2Req,
 } from '@/core/entities';
 import { GeneralCallResult } from '@/core/services/common';
 
 //高版本的接口不应该随意使用 使用应该严格进行pr审核 同时部分ipc中未出现的接口不要过于依赖 应该做好数据兜底
 
 export interface NodeIKernelGroupService {
+    kickMemberV2(param: kickMemberV2Req): Promise<GeneralCallResult>;
     quitGroupV2(param: { groupCode: string; needDeleteLocalMsg: boolean; }): Promise<GeneralCallResult>;
-    
+
     getMemberCommonInfo(Req: {
         groupCode: string,
         startUin: string,