Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Get rid of $input
See original GitHub issueWhen using arguments in subscriptions you need to use $input argument instead of passing arguments separate.
This behavior comes from mutations and I’m not sure what the tradeoffs are to get rid of it or if it is even possible without modifying the babel plugin.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
How to Remove and Style the Border Around Text Input Boxes ...
Remove the outline and add a border style using the :focus and :active pseudo-classes with the <input> field. Also, you can remove the...
Read more >How to remove input methods that automatically appeared in ...
Press Windows key + I and access Time and Language; Click Language and Region; Click (...) which will be to the right of...
Read more >How to remove focus border (outline) around text/input boxes ...
This border is used to show that the element is focused (i.e. you can type in the input or press the button with...
Read more >How to Remove Outline around Text Input Boxes in Chrome ...
Answer: Use CSS outline property. In Google Chrome browser form controls like <input> , <textarea> and <select> highlighted with blue outline ...
Read more >How To Get NO INPUT DELAY On Your Keyboard ... - YouTube
How To Get NO INPUT DELAY On Your Keyboard! ( Get Lower Latency)In this video I explain how you can fix any Input...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
How I know, it just Relay architectural solution. Graphql and babel-plugin do not have such restriction. So if you ommit this wrap field, your subscriptions and relay mutations will have different symantics. So on server side we lost ability to reuse some resolve function from mutation. That just trade-off.
My opinion we should keep this field, while working under Relay, due relay arch design.
Awesome @trbngr!