Gatling version:
Gatling flavor: java kotlin scala javascript typescript
Gatling build tool: maven gradle sbt bundle npm
Hi all,
I have an issue with Gatling typescript and grpc.
I have in protobuf folder that structure :
- protobuf
- google
- protobuf
- “standards google proto files”
- protobuf
- com
- xxx
- mobile
- common
- v1
-
models
- protos with import dependencies from “types”
-
services
- protos with import dependencies from “models” and “types”
-
types
-
- v1
- common
- mobile
- xxx
- google
exemple of proto import in models proto’s :
syntax = “proto3”;
package com.xxx.mobile.common.v1.models;
import “com/xxx/mobile/common/v1/models/multi_lang_string.proto”;
import “com/xxx/mobile/common/v1/types/agreement_acceptance_method.proto”;
import “com/xxx/mobile/common/v1/types/agreement_type.proto”;
import “com/xxx/mobile/common/v1/types/agreement_show_at.proto”;import “google/protobuf/wrappers.proto”;
message Agreement {
string id = 1;…
When I try to launch a simple simulation, gatling fails at the beginning during proto transformation
Bundling a Gatling simulation with options:
sourcesFolder: src/simulations
protoFolder: protobuf
bundleFile: target/bundle.js
com/xxx/mobile/common/v1/models/multi_lang_string.proto: File not found.
com/xxx/mobile/common/v1/types/agreement_acceptance_method.proto: File not found.
com/xxx/mobile/common/v1/types/agreement_type.proto: File not found.
com/xxx/mobile/common/v1/types/agreement_show_at.proto: File not found.
google/protobuf/wrappers.proto: File not found.
All theses files are actually available.
Any ideas ? is there any limitation with that complex hierarchy ?