When using @8base-js-sdk/api (v0.1.6) from npm, when initializing a subscription to a workspaceId that corresponds to a child environment of the Master environment, it causes the subscription to error out saying “Workspace not found”. However, when using the Master workspaceId, the subscription works fine.
An example of what I mean when I say the workspaceId being a child environment would be where envr123 is the Master environment; a child environment would be envr123_Development or envr123_Staging.
I’m not sure if this is the intended behavior or not, but I would hope it’s not. To strictly only allow GraphQL subscriptions on the Master environment would be a huge flaw and a real deal breaker for any application that makes use of multiple database environments for the purposes of development or staging environments that don’t affect production data.
If there is anything I’m simply missing please let me know because we would really like to make use of this package if possible.
Edit:
This same problem can be found on multiple other community posts as well. The first example there seemed to be no resolution for, however, the other 2 seem to be resolved by defining an environmentName to identify the child environment. This concept does not seem to exist on this @8base-js-sdk/api package (I also looked at the typescript file to see for sure what properties are acceptable and saw nothing of the sort)