muxrpc #6
Open
muxrpc #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sorry - as long as there are no typedefs for muxrpc AND there is no other contributure that actually wants TS for this, I'm not willing to put up with this and rather go for thorough testing and lining.
|
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
|
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm moving the IO between nodejs systray and systrayhelper from home-grown json to muxrpc.
sorry to drop typescript along the way. I can see the benefits but fighthing against upstream deps that don't use it feels very don quixote. standardjs and testing gives me enough feeling of safty for now, at least for undefined checks.