Handle calling Publish() on another module's topic #1640
Assignees
Comments
Open
|
This should be an error. Ideally we'd pick this up statically. |
matt2e
added a commit
that referenced
this issue
Jun 11, 2024
Closes #1640 Checks for: - publishing directly to an external module's exported topic - directly calling an external module's verb, rather than using `ftl.Call(...)` - This already fails at runtime, but it's nice to have this as a compile error Both of these compile-time checks are not fool proof, any indirection will mean these checks don't catch it. But it is good to catch what we can. eg: ```go var extTopic = external.Topic extTopic.Publish(...) // compiler believes this is a local topic ``` Added a separate issue for this for pubsub as it may not be as high a priority: #1703
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Either return an error or make it work.
Currently it sends the callees module name which could cause very weird issues.
The text was updated successfully, but these errors were encountered: