Snippets | Snippts in various languages | Parser library

The field statusCode is mutable on the returned object. Thus, if changed, the type would no longer be the same which breaks type safety.

I removed limitations the developer supposed to limit in design.graeco() function, I honestly didnt know why there should be limitation on specific lengths on treatment, here is the final result of no limitation with Graeco Latin Square designs

The line

In the post method of your UpdateView, you're trying to return a JsonResponse

You can use

You forgot () in the function declaration of test, and there were a couple of document.getElementById's for non-existent html elements with non-existent functions.

See below, it works perfectly fine.

Since object like "QuadTypeIndependenceTest" and "ScalarIndependenceTest" are created from the results of coin packages, there is specific function to extract the pvalue, using coin::pvalue(obj), Special thanks for pointing @AntoniosK

While I can certainly change the context of $(this) by using $.call(Object, argument) or doing an Object.assign({}, object) somewhere in the code, to manipulate the $.fn.init(selector, context) of jQuery, I have decided to create an alternative Vanilla solution Framework.

And, while jQuery is worth pursuing, I have built this custom CORE jQuery support library in stead. In other words, this framework mimics everything in the jQuery syntax as shown in the minimum code example. I believe that this is also the missing manual that most developers need that is virtually impossible to search these days in the internet due to jQuery's popularity & search ranking wars.

The goal as mentioned in the OP is to try to include only as little jQuery code as possible or implement an alternative solution with the jQuery snippet as needed because jQuery has grown so huge with newer versions and extensions and most of those code have considerable performance overhead other than the learning curve.

With this new CORE, I can easily extend support for jQuery, with $.fn.extend or $.extend or $.prototype.extend and for future use cases whenever the need arises, do another plugin for some basic routines or re-plug $(function()}) or $(document.ready()}) or implement other custom filters and jQuery-like chores, some of which I have already built and stripped off from this code such as event handlers and the $.ajax.

The good news is, we can even reuse already built favorite jQuery plugins without having to worry about compatibility issues because the power of jQuery is already in our hands! The core also preserved our favorite dot notation among others! :D

Overall, this is very handy whenever building minimal, manageable, reusable, modular Javascript, as well as building on top of the missing Vanilla learning curve and understanding how browsers work, especially because the heart of jQuery which is the $.extend is herein preserved. Some of the mechanics of this library though (about 2% of the code), is ported from jQuery and I'm planning to build on top of this CORE for my projects without having to worry about licenses.

That said, I hope this will be helpful to some developers out there. I'm licensing this code with MIT.