add a list api for GET methods

.github/RELEASE.md

@@ -1,5 +1,5 @@
 ## Change log
 
-- Sponge command ui service support docker deployment.
-- Adjustment option code.
-
+- Fix bug with naocs as service discovery.
+- Add support for distributed transaction manager [DTM](https://github.com/dtm-labs/dtm).
+- Add a list api interface for GET methods.

Makefile

@@ -104,7 +104,7 @@ build-sponge:
 # build a sponge docker image, e.g. make image-build-sponge TAG=v1.5.8
 image-build-sponge:
 	@echo "build a sponge docker image'"
-	@cd cmd/sponge/scripts && bash image-build.sh  $(TAG)
+	@cd cmd/sponge/scripts && bash build-sponge-image.sh  $(TAG)
 
 # delete the templates code end
 

README.md

@@ -18,9 +18,9 @@
 
 <br>
 
-If you are developing a web or microservice with a simple CRUD API interface, you don't need to write a single line of golang code to compile and deploy to servers, dockers, k8s, and the complete service code is generated by sponge.
+If you are developing a RESTful web or microservice with a simple CRUD API interface, you don't need to write a single line of golang code to compile and deploy to servers, dockers, k8s, and the complete service code is generated by sponge.
 
-If you develop a generic web or microservice, you need to manually write code in addition to defining the data table, defining the api interface in the proto file, and filling in the specific business logic code in the generated template file. Other golang codes are generated by sponge.
+If you develop a generic RESTful web or microservice, you need to manually write code in addition to defining the data table, defining the api interface in the proto file, and filling in the specific business logic code in the generated template file. Other golang codes are generated by sponge.
 
 <br>
 
@@ -108,6 +108,10 @@ No specific business logic code is included.
 - [7_community-single](https://github.com/zhufuyi/sponge_examples/tree/main/7_community-single)
 - [8_community-cluster](https://github.com/zhufuyi/sponge_examples/tree/main/8_community-cluster)
 
+#### Distributed transaction examples
+
+- [9_order-system](https://github.com/zhufuyi/sponge_examples/tree/main/9_order-grpc-distributed-transaction)
+
 <br>
 
 **If it's help to you, give it a star ⭐.**

api/serverNameExample/v1/userExample.proto

@@ -159,6 +159,23 @@ service userExample {
     };
   }
 
+  // list userExample by last id
+  rpc ListByLastID(ListUserExampleByLastIDRequest) returns (ListUserExampleByLastIDReply) {
+    option (google.api.http) = {
+      get: "/api/v1/userExample/list"
+    };
+    option (grpc.gateway.protoc_gen_openapiv2.options.openapiv2_operation) = {
+      summary: "list of userExamples by last id",
+      description: "list of userExamples by last id",
+      //security: {
+      //  security_requirement: {
+      //    key: "BearerAuth";
+      //    value: {}
+      //  }
+      //}
+    };
+  }
+
   // list of userExample by query parameters
   rpc List(ListUserExampleRequest) returns (ListUserExampleReply) {
     option (google.api.http) = {
@@ -282,6 +299,16 @@ message ListUserExampleByIDsReply {
   repeated UserExample userExamples = 1;
 }
 
+message ListUserExampleByLastIDRequest {
+  uint64 lastID = 1 [(tagger.tags) = "form:\"lastID\""]; // last id
+  uint32 limit = 2 [(tagger.tags) = "form:\"limit\""]; // page size
+  string sort = 3 [(tagger.tags) = "form:\"sort\""]; // sort by column name of table, default is -id, the - sign indicates descending order.
+}
+
+message ListUserExampleByLastIDReply {
+  repeated UserExample userExamples = 1;
+}
+
 message ListUserExampleRequest {
   types.Params params = 1 [(validate.rules).message.required = true];
 }