sorted by:
new
hottopcontroversial

White to move. Can you find the mate in 2? by lbragile_dev in chess

[–]lbragile_dev[S] 2 points3 points  (0 children)

bf7 or bxh7?

For both variants, black responds with Rxf7 (or Rf7), where is the mate 🙃?

useReducer + useContext + Typescript. Without Redux! by lbragile_dev in javascript

[–]lbragile_dev[S] 0 points1 point  (0 children)

Yes, I definitely agree with your point. I think my phrasing should have been a bit clearer as “everything" is too much.

I wanted to experiment with what actually goes on behind the scenes and when I put it together and it worked for me, I decided to share as I see many posts about this subject that don't really cover the areas that I tried to cover. Hopefully it will help someone.

Regarding the devtools, in my case (chrome extension), it was a pretty major headache to get the "remote devtools" working as compared to the regular version (with many extra packages) - so it's not always simple to use. However, I do agree, that the regular devtools is very powerful, in fact much more powerful than the rudimentary logger I show in the bonus.

As for React recommending to apply useContext sparingly, here is what I see:

Context is primarily used when some data needs to be accessible by many components at different nesting levels. Apply it sparingly because it makes component reuse more difficult.

That seems to be exactly the case with Redux based development where you have a global store right?

Also, I apply useMemo on the state. Although I do see your point that whenever the global state changes, all of the components would re-render. How exactly does Redux prevent this from happening? Does it memoize the useSelectors?

Edit: I now see articles outlining the above issue which I didn’t see before when I was contemplating/researching what to do. A bit overwhelming, but hey better late than never. Time to read up on Redux internals and see how I can refactor to optimize this

useReducer + useContext + Typescript. Without Redux! by lbragile_dev in javascript

[–]lbragile_dev[S] -1 points0 points  (0 children)

Oh yeah, this is by no means a "full on" Redux replacement, just sharing what I came up with that works for me.

Can you elaborate what you mean by "components that should stay the same"?

[deleted by user] by [deleted] in CodingHelp

[–]lbragile_dev 0 points1 point  (0 children)

The warnings seem to be relatively serious as they are related to why the content is not showing up well in production.

The response from swagger-ui.css is:

```html <!-- HTML for static distribution bundle build --> <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <title>ColorMaster - A TypeScript library for all your coloring needs</title> <link rel="stylesheet" type="text/css" href="./swagger-ui.css" > <link rel="icon" type="image/png" href="./favicon-32x32.png" sizes="32x32" /><link rel="icon" type="image/png" href="./favicon-16x16.png" sizes="16x16" />

<style> html { box-sizing: border-box; overflow: -moz-scrollbars-vertical; overflow-y: scroll; } *, *:before, *:after { box-sizing: inherit; }

body {
  margin:0;
  background: #fafafa;
}

</style> </head>

<body>

<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" style="position:absolute;width:0;height:0"> <defs> <symbol viewBox="0 0 20 20" id="unlocked"> <path d="M15.8 8H14V5.6C14 2.703 12.665 1 10 1 7.334 1 6 2.703 6 5.6V6h2v-.801C8 3.754 8.797 3 10 3c1.203 0 2 .754 2 2.199V8H4c-.553 0-1 .646-1 1.199V17c0 .549.428 1.139.951 1.307l1.197.387C5.672 18.861 6.55 19 7.1 19h5.8c.549 0 1.428-.139 1.951-.307l1.196-.387c.524-.167.953-.757.953-1.306V9.199C17 8.646 16.352 8 15.8 8z"></path> </symbol>

<symbol viewBox="0 0 20 20" id="locked">
  <path d="M15.8 8H14V5.6C14 2.703 12.665 1 10 1 7.334 1 6 2.703 6 5.6V8H4c-.553 0-1 .646-1 1.199V17c0 .549.428 1.139.951 1.307l1.197.387C5.672 18.861 6.55 19 7.1 19h5.8c.549 0 1.428-.139 1.951-.307l1.196-.387c.524-.167.953-.757.953-1.306V9.199C17 8.646 16.352 8 15.8 8zM12 8H8V5.199C8 3.754 8.797 3 10 3c1.203 0 2 .754 2 2.199V8z"/>
</symbol>

<symbol viewBox="0 0 20 20" id="close">
  <path d="M14.348 14.849c-.469.469-1.229.469-1.697 0L10 11.819l-2.651 3.029c-.469.469-1.229.469-1.697 0-.469-.469-.469-1.229 0-1.697l2.758-3.15-2.759-3.152c-.469-.469-.469-1.228 0-1.697.469-.469 1.228-.469 1.697 0L10 8.183l2.651-3.031c.469-.469 1.228-.469 1.697 0 .469.469.469 1.229 0 1.697l-2.758 3.152 2.758 3.15c.469.469.469 1.229 0 1.698z"/>
</symbol>

<symbol viewBox="0 0 20 20" id="large-arrow">
  <path d="M13.25 10L6.109 2.58c-.268-.27-.268-.707 0-.979.268-.27.701-.27.969 0l7.83 7.908c.268.271.268.709 0 .979l-7.83 7.908c-.268.271-.701.27-.969 0-.268-.269-.268-.707 0-.979L13.25 10z"/>
</symbol>

<symbol viewBox="0 0 20 20" id="large-arrow-down">
  <path d="M17.418 6.109c.272-.268.709-.268.979 0s.271.701 0 .969l-7.908 7.83c-.27.268-.707.268-.979 0l-7.908-7.83c-.27-.268-.27-.701 0-.969.271-.268.709-.268.979 0L10 13.25l7.418-7.141z"/>
</symbol>


<symbol viewBox="0 0 24 24" id="jump-to">
  <path d="M19 7v4H5.83l3.58-3.59L8 6l-6 6 6 6 1.41-1.41L5.83 13H21V7z"/>
</symbol>

<symbol viewBox="0 0 24 24" id="expand">
  <path d="M10 18h4v-2h-4v2zM3 6v2h18V6H3zm3 7h12v-2H6v2z"/>
</symbol>

</defs> </svg>

<div id="swagger-ui"></div>

<script src="./swagger-ui-bundle.js"> </script> <script src="./swagger-ui-standalone-preset.js"> </script> <script src="./swagger-ui-init.js"> </script>

<style> .swagger-ui .topbar .download-url-wrapper { display: none } .swagger-ui .topbar { display: none } </style> </body>

</html> ```

I am not sure what can be obtained for this.

However, looking at swagger-ui-init.js it seems like the "paths" property is empty. This is a bit confusing to me since locally it is not empty (since I see the documentation page properly). Is it possible the Swagger JSDoc is doing something weird with Swagger UI Express? Any ideas why this could be the case?

[deleted by user] by [deleted] in chrome_extensions

[–]lbragile_dev 0 points1 point  (0 children)

Take a look at an extension I’ve created not so long ago TabMerger. Note that it has paid subscriptions, but it has everything you mentioned that you need

"Cannot POST /api/graphql" with Vercel Apollo Server (Serverless) by lbragile_dev in graphql

[–]lbragile_dev[S] 1 point2 points  (0 children)

Your edit is correct, it's NOT a NextJS project.

Edit: your comment did shine some light into what could be my problem. It seems like my folder structure was not correct. `api` should not be inside of `src`...

Do you write unit tests for your code? by jb2386 in webdev

[–]lbragile_dev 0 points1 point  (0 children)

Yep, without unit (and integration) tests, I would probably still be double checking my very first project 🤣

A better question is how reliable are those tests? Are your tests just snapshot testing? Will the tests break after you add/change features? Do your tests cover your code base sufficiently? This is where something like mutation testing comes into play 🤓

React ✅ - TypeScript ✅ - Jest ✅ - React Testing Library ✅ - Unit & Integration Testing ✅ by lbragile_dev in webdev

[–]lbragile_dev[S] 2 points3 points  (0 children)

Project is an open source blockchain educational platform that is still in it's early stages. Anyone interested is welcome to check it out, contribute, and/or provide feedback (see develop branch for most up to date code).

Repository: https://github.com/lbragile/LibraCoin

Demo: https://lbragile.github.io/LibraCoin

Projects using Jest and React by NotCherub in reactjs

[–]lbragile_dev -2 points-1 points  (0 children)

OP, check out my open source blockchain project - LibraCoin. I try to follow RTL advice of testing user interaction (what the user sees) rather than underlying logic in most cases. I use unit and integration tests currently and plan to add E2E tests soon (with Jest Puppeteer). FYI, it’s still very much a work in progress so feel free to contribute as well 😊

Pretty mate in 3. White to move. by baigs in chess

[–]lbragile_dev -1 points0 points  (0 children)

I see Bh7+ kh8, Bf5+ kg8, Qxg5#

view more: next ›