3 ms·
Offtopic, but as someone who hasn't done a lot of JS recently, debugging something like this looks like a terrible job. I assume the non-sensible function/obje
by tyingq 8y ago
Offtopic, but as someone who hasn't done a lot of JS recently, debugging something like this looks like a terrible job. I assume the non-sensible function/object names are the result of some kind of packer? Do modern JS folks have to recreate this sort of thing in a pre-packed environment to track it down more easily?
- cdmckay 8y agoYou can use source maps to debug it
- andrenotgiant 8y agoThe author published all the content and code on gitlab, here is the logic for the pricing calculator: https://gitlab.com/barnabas/barnabas.gitlab.io/blob/master/docs/.vuepress/components/DbaasCalculator.vue https://gitlab.com/barnabas/barnabas.gitlab.io/blob/master/d...
- tyingq 8y agoAh, thanks. And the fix was: https://gitlab.com/barnabas/barnabas.gitlab.io/commit/f7fedea54a3be8046df8d7e753cfb7f69fc870b9#289a33df87be2b903369ee3b4c88a22d9fc4a920_121_138 https://gitlab.com/barnabas/barnabas.gitlab.io/commit/f7fede...
- deleted 8y ago[deleted]