Johan Andrén
Johan Andrén
See the ACL integration test action. It also lacks a sample in the docs, might be a good thing to fix in one go.
So that each deploy will update the service (without having to change the version in package.json for each deploy) Sparked by https://github.com/lightbend/kalix-jvm-sdk/pull/937#pullrequestreview-957373833
Not sure what is the expected behavior in general by JS/TS devs but in the Java SDK we treat a `.failure(...)` response as a validation error or expected failure that...
ScalaPB has a special quirky feature which is that a protobuf `oneof` with the name `sealed_[name]` will generate a sealed ADT (docs: https://scalapb.github.io/docs/sealed-oneofs/) however that generates types that the SDK...
Like pipe character not allowed, [dashes not allowed](https://github.com/lightbend/kalix-jvm-sdk/issues/1837), and how long they can be.
Now that the `IntegrationTest` config in sbt is deprecated we need a different way to run integration tests, preferably allowing to run them separately from unit tests. The sbt recommendation...
Reported in the forum: https://discuss.kalix.io/t/when-is-valueentitys-currentstate-updated/330 ``` effects().updateState(... new state ...).thenReply(currentState()) ``` Returns the previous state rather than the updated state from `currentState()`. I think it should return the updated state.
Even the generated sources directories are not always picked up correctly. _Originally posted by @ennru in https://github.com/lightbend/kalix-jvm-sdk/issues/383#issuecomment-1104882576_ Let's make this a separate issue from the one about protobuf dependencies not...
I get this, not sure it is a problem but users will also not be sure if it is a problem or not. ``` [warn] /Users/johan/Code/blablabla/target/scala-2.13/akka-grpc/main/kalix/DirectSource.scala:18:63: Variable MY_ENV_NAME undefined in...
As it is a part of our test coverage for the integration-testkit.