Skip to content

WIP: Make dispatcher private objects truly private#21

Open
1000TurquoisePogs wants to merge 1 commit intozowe:v1.x/stagingfrom
1000TurquoisePogs:feature/private-dispatcher
Open

WIP: Make dispatcher private objects truly private#21
1000TurquoisePogs wants to merge 1 commit intozowe:v1.x/stagingfrom
1000TurquoisePogs:feature/private-dispatcher

Conversation

@1000TurquoisePogs
Copy link
Copy Markdown
Member

The "private" keyword of typescript doesn't really make objects private at runtime. Returning an anomyous object that fulfills the shape of the interface allows for objects that were private to be omitted and kept truly private.
Some of the functions in the dispatcher object weren't in the interface, and were therefore implicitly private. Typescript complained at this and so they were made private. Anyone who was using these would have gotten a typescript type definition warning so I'm assuming people weren't.

Signed-off-by: 1000TurquoisePogs sgrady@rocketsoftware.com

…d action arrays private

Signed-off-by: 1000TurquoisePogs <sgrady@rocketsoftware.com>
@1000TurquoisePogs 1000TurquoisePogs requested a review from a team February 7, 2019 19:46
@ghost ghost added the review label Feb 7, 2019
@1000TurquoisePogs 1000TurquoisePogs changed the base branch from master to staging March 8, 2019 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant