Skip to content
This repository has been archived by the owner on May 10, 2024. It is now read-only.

[RTC-117] Move typed emitter to runtime deps #31

Merged
merged 1 commit into from
Jun 6, 2023
Merged

Conversation

mickel8
Copy link
Contributor

@mickel8 mickel8 commented Jun 5, 2023

Shouldn't TypedEmitter be in runtime deps? I can see that it's in dev deps in ts-client-sdk but when it's in dev deps, VSCode cannot see on property on WebRTCEndpoint class 🤔

@LVala
Copy link
Member

LVala commented Jun 6, 2023

Are you sure? Language Server was suggesting events names in Neovim just fine when I was modifying integration tests in membrane_rtc_engine (after building it with npm run build). I'll check it once more tho.

Copy link
Member

@LVala LVala left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've checked it and you're right, although for some reason when building locally, it worked fine, maybe wait for @kamil-stasiak comment as I'm no expert on typescript.

@mickel8 mickel8 changed the title Move typed emitter to runtime deps [RTC-117] Move typed emitter to runtime deps Jun 6, 2023
@mickel8 mickel8 merged commit cf48dc8 into master Jun 6, 2023
@mickel8 mickel8 deleted the typped-emitter branch June 6, 2023 14:08
@mickel8
Copy link
Contributor Author

mickel8 commented Jun 6, 2023

@ostatni5 said it looks ok so I am merging

@ostatni5
Copy link
Contributor

ostatni5 commented Jun 6, 2023

According to stackoverflow, if types are exposed to the library user, they should be in dependencies.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants