Skip to content

[Move] Restrict types of values that can be fired as events #2662

Open
@awelc

Description

@awelc

At this point we throw an error to indicate that an event has been fired with a primitive value as an argument. The proposal here (as discussed with @tnowacki) is t to restrict what value types can be used as arguments when firing events even further, that is to structs defined in the same module that fires the event.

A primitive value event is pretty meaningless as it carries minimal amount of information, but using an arbitrary struct type is also not very informative as it makes it difficult to find out which module was responsible for firing the event.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Priority: MediumA nice to have feature or annoying bug, non-blocking and no delays expected if we punt on itTriagedIssue is associated with a milestone and has at least 1 label of each: status, type, & priorityType: EnhancementNew feature or requestmove

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions