Add linters (#73)

* Add linters

* Yaml lint fixes

* Yaml lint fixes

* Yet another lint fixes

* Need more yaml lint fixes

* I thinkб its last fixes with yaml lint

.github/workflows/basic-linters.yml

@@ -0,0 +1,10 @@
+name: Vality basic linters
+
+on:
+  pull_request:
+    branches:
+      - "*"
+
+jobs:
+  lint:
+    uses: valitydev/base-workflows/.github/workflows/basic-linters.yml@v1

.github/workflows/build-java-lib.yml

@@ -3,7 +3,7 @@ name: Build java libraries
 on:
   pull_request:
     branches:
-      - '*'
+      - "*"
 
 jobs:
   build:

.github/workflows/build-v2.yml

@@ -8,15 +8,15 @@ on:
 jobs:
   build:
     runs-on: ubuntu-latest
-    
-    steps:  
+
+    steps:
       - name: Checkout code
         uses: actions/checkout@v3
-      
+
       - name: Setup Node
         uses: actions/setup-node@v3
         with:
-          node-version: '16'
+          node-version: "16"
 
       - name: Cache Node Modules and NPM Cache
         id: cache
@@ -26,13 +26,13 @@ jobs:
             node_modules
             ~/.npm
           key: ${{ runner.os }}-node-${{ hashFiles('package-lock.json') }}
-      
+
       - name: Install deps
         if: steps.cache.outputs.cache-hit != 'true'
         run: npm install
-      
+
       - name: Run tests
         run: npm test
-      
+
       - name: Bundle spec and build docsite
         run: npm run build

.github/workflows/frontend-pr.yml

@@ -1,8 +1,8 @@
-name: 'Frontend: PR'
+name: "Frontend: PR"
 
 on:
   pull_request:
-    branches: ['*']
+    branches: ["*"]
 
 jobs:
   configured:

.github/workflows/frontend-publish.yml

@@ -1,8 +1,8 @@
-name: 'Frontend: Publish'
+name: "Frontend: Publish"
 
 on:
   push:
-    branches: ['master', 'main', 'v2']
+    branches: ["master", "main", "v2"]
 
 jobs:
   configured:
@@ -23,4 +23,4 @@ jobs:
       - uses: valitydev/action-frontend/publish@v0.1
         with:
           npm-token: ${{ secrets.NPM_TOKEN }}
-          directory: ./lib
+          directory: ./lib

.github/workflows/release-erlang-v2.yml

@@ -41,11 +41,20 @@ jobs:
         run: npm run build -- web_deploy
 
       - name: Generate stubs
-        run: |
+        run: >
           mkdir -p out
-          swagger-codegen generate -l vality-erlang-client -i web_deploy/swagger.json -o out/erlang-client --additional-properties packageName=swag_client
-          swagger-codegen generate -l vality-erlang-server -i web_deploy/swagger.json -o out/erlang-server --additional-properties packageName=swag_server
 
+          swagger-codegen generate
+          -l vality-erlang-client
+          -i web_deploy/swagger.json
+          -o out/erlang-client
+          --additional-properties packageName=swag_client
+
+          swagger-codegen generate
+          -l vality-erlang-server
+          -i web_deploy/swagger.json
+          -o out/erlang-server
+          --additional-properties packageName=swag_server
       - name: Deploy erlang-client artifact to release branch
         uses: JamesIves/github-pages-deploy-action@v4.3.3
         with:

.github/workflows/release-java-lib.yml

@@ -1,7 +1,7 @@
 name: Release java libraries
 on:
   push:
-    branches: ['master', 'main', 'v2']
+    branches: ["master", "main", "v2"]
 
 jobs:
   deploy:

spec/definitions/MobileOperator.yaml

@@ -1,6 +1,8 @@
 description: >
   Cellular operator.
 
-  The list of operators available for making payments can be found out by calling the corresponding [operation](#operation/getInvoicePaymentMethods) after creating an invoice.
+  The list of operators available for making payments can be found out by
+  calling the corresponding [operation](#operation/getInvoicePaymentMethods)
+  after creating an invoice.
 type: string
 example: MTS

spec/paths/processing@invoices@{invoiceID}@fulfill.yaml

@@ -4,27 +4,23 @@ post:
     - Invoices
   operationId: fulfillInvoice
   parameters:
-    - 
-      $ref: '#/parameters/requestID'
-    - 
-      $ref: '#/parameters/deadline'
-    - 
-      $ref: '#/parameters/invoiceID'
-    - 
-      name: fulfillInvoice
+    - $ref: "#/parameters/requestID"
+    - $ref: "#/parameters/deadline"
+    - $ref: "#/parameters/invoiceID"
+    - name: fulfillInvoice
       in: body
       description: Reason for the operation
       required: true
       schema:
-        $ref: '#/definitions/Reason'
+        $ref: "#/definitions/Reason"
   responses:
-    '204':
+    "204":
       description: Инвойс погашен
-    '404':
-      $ref: '#/responses/NotFound'
-    '401':
-      $ref: '#/responses/Unauthorized'
-    '400':
+    "404":
+      $ref: "#/responses/NotFound"
+    "401":
+      $ref: "#/responses/Unauthorized"
+    "400":
       description: Invoice fulfillment error
       schema:
         type: object

spec/swagger.yaml

@@ -339,6 +339,7 @@ tags:
 
   - name: Invoices
     x-displayName: Invoices
+    # yamllint disable rule:line-length
     description: >
       An invoice is a fundamental model for work with payment acceptance
       system. It is necessary to create an invoice and find out its ID before
@@ -440,7 +441,7 @@ tags:
         * AllocationFeeFixed or fee amount in favour of an invoice shop.
 
         * AllocationFeeShare or some percent of the total amount of transaction in favour of an invoice shop.
-
+  # yamllint enable rule:line-length
   - name: InvoiceTemplates
     x-displayName: Invoice templates
     description: >
@@ -498,7 +499,8 @@ tags:
       The debiting (capturePayment) can be confirmed on equal or less
       authorisation amount. If the less amount is specified, the balance will
       be refunded to a payer. The successful authorisation can be confirmed or
-      cancelled both manually by calling the corresponding API method (capturePayment or cancelPayment) and automatically according to the
+      cancelled both manually by calling the corresponding API method
+      (capturePayment or cancelPayment) and automatically according to the
       chosen strategy onHoldExpiration. The manual confirmation period is set
       in the system settings by yourself and it is usually from 3 to 7 calendar
       days.
@@ -606,6 +608,7 @@ tags:
       processes.
   - name: Error Codes
     x-displayName: Error codes
+    # yamllint disable rule:line-length
     description: >
       ## Business logic errors
 
@@ -622,7 +625,7 @@ tags:
 
 
       The error type is in the field `code` and additional information about
-      the error that occurred is in `message`. 
+      the error that occurred is in `message`.
 
       There are the following error codes at the present moment:
 
@@ -631,7 +634,7 @@ tags:
       |----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|
 
       | **operationNotPermitted**        | Unavailable transaction within the current contract.                                                                                       |
-      
+
       | **invalidPartyStatus**           | Your participant is blocked or its transactions has been suspended. In the latter case, you can [resume](#operation/activateMyParty) them. |
 
       | **invalidShopStatus**            | Your shop is blocked or its transactions has been suspended. In the latter case, you can [resume](#operation/activateShop) them.           |
@@ -903,3 +906,4 @@ tags:
       ```
 
       If you have an error that is not described here, contact the technical support.
+# yamllint enable rule:line-length