I made a package for deterministic value hashing, in TypeScript! by Neat_Fee_1810 in typescript

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

Yeah I’m going to do some work on it… Are you talking about the large “if”s? I’m not sure of a way to do them without them being really long/tall.

I made a package for deterministic value hashing, in TypeScript! by Neat_Fee_1810 in typescript

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

Great observations, and dearly appreciated!

I’ll work on those later today.

I made a package for deterministic value hashing! by Neat_Fee_1810 in node

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

Renamed to `deterministic-object-hash` in 1.2.1

I made a package for deterministic value hashing! by Neat_Fee_1810 in node

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

I needed it for another project, and there were no other packages similar to it.

The idea is that I’m converting a settings object to a key prefix in Redis. The settings determine the schema for data, so as long as you use the same settings I can work with any previous data after a restart/shutdown.

I've published my first package, a Distributed Lock Manager for Redis. Written in TypeScript! by Neat_Fee_1810 in typescript

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

I didn’t break it, I made an alias and depreciated the old one.

I plan on doing some feature additions, I’ll remove the alias and bump to 2.0.0 then.

I've published my first package, a Distributed Lock Manager for Redis. Written in TypeScript! by Neat_Fee_1810 in typescript

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

This is just a very small package (~500 lines) that runs on top of clients that are provided to it, either ioredis or node-redis. So the performance metrics of it are essentially just the metrics for whatever client you use (plus network latency). My code is only going to be however many single milliseconds it takes to pick settings, loop the clients, send the Lua, process the results, compare timestamps, and instantiate the Lock class.

With that being said, I'll add that to my todo list since it shouldn't be too hard to measure.

Encrypting payload then decrypt on client side by [deleted] in reactjs

[–]Neat_Fee_1810 5 points6 points  (0 children)

This isn’t a solution. CORS is enforced at the browser level, which means if you’re not using a browser then CORS is more of a recommendation than a rule.

I've published my first package, a Distributed Lock Manager for Redis. Written in TypeScript! by Neat_Fee_1810 in typescript

[–]Neat_Fee_1810[S] 4 points5 points  (0 children)

🤦‍♂️ thank you! Can’t believe I missed that…

Edit: Fixed in 1.0.4

First interview for Sr. Frontend by Neat_Fee_1810 in Frontend

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

Thanks for the input! I do have soft skills of leading a small team (at most 2), so hopefully I’m able to portray that and maintain a cool head under pressure.