Problem: If an app makes multiple GraphQL calls on the same page, all the GraphQL calls look the same in the network tab.
My approach: Click on each call, one by one, to view the payload's query name.
This is time-consuming.
Anyone have a trick for this?
A cure for React useState hell?
You may not realize how easily you can replace useState with useReducer and simplify your state management
You can read more in my latest blog post: https://t.co/TaI5MOQycS
⚛️ React tip: when conditionally rendering component based on some string enum (like a role), use an object to map enum values to components.
This can be cleaner than using conditional operators, and it keeps the logic organized & clear.
Use-case coverage is far more important than code coverage.
You can have 100% code coverage and still have your app break in prod.
Use cases can be encoded in end-to-end (E2E) tests, which will produce tests that are as close as possible to how an app will actually be used ✅
எட்டு போட்டு நடந்தா மூட்டு வலி வரும். தெரியாம நானும், காலையில் நாய்த்தொல்லை அதிகமா இருக்கேன்னு வீட்டுல எட்டு மாதிரி நடந்தேன். மூணே மாசம். அதுவரை தரையில் உட்கார்ந்து சாப்பிட்டவன் இப்போ டைனிங் டேபிள்ள சாப்பிடுற மாதிரி ஆயிருச்சு.
@ansankarganesh I think, It will be useful who earns more than 15 lacs. We can’t claim the deduction for HRA, medical other than the standard deduction 50k
Curious about upcoming Lightning Web Components features? In the latest #SFDevPod we're discussing these upcoming features, the migration of Aura components over to LWC and more: https://t.co/nSoMa3RlYY
🥳@FlutterDev X @CodePen 🥳
Announcing CodePen support for Flutter! We hope this new playground will empower you to build animations and showcase your creativity.
💙Share your designs with us using #FlutterPen.
Learn more here → https://t.co/OpTP9KuUeV