globalize | JavaScript library for internationalization | Internationalization library

You setup localization correctly, though your localizer would first require setting a default timezone. First, you'd have to be using moment-timezone. By default it uses your user's default (browser local) timezone. To change that, you can reset the default timezone used by moment.

This is a very Opinion Based question. I would say Both, But in suitable places.

Tiny Short Classes

These types of classes are common in Bootstrap and Tailwind. This will help us to apply styles in a very flexible way. But also too many classes will reduce the Code Readability.

Specific Classes (Component)

This will help to minimize classes and apply a set of styles to the particular element/component. But obviously not flexible.

In React, Use Both

One of the major advantages of React is re-usable components. When we say re-usable, The component is standard/common that can be appeared in many other places. In that case, using too many tiny classes will be messy.

So, Always use Specific Component Classes for common components of the application. And use Tiny Short Classes for some additional styles or rare components.

In Other Hand, When a component exceeds 4 - 5 short classes, and if the component appears in many places in the app, Please use a component class as the wrapper of those short classes.

Don't, instead use return values:

Generally speaking, in your .where method you should use the real table name, not the relationship's name between your models, so try with:

Redeclaring a variable in an inner scope creates a new variable.

I found a solution to handle pagination button count globally

Assuming in your parent component you're correctly initializing FormGroup in controller and using it correctly in template, you have two main errors in your component.

First, as Belle Zaid says, you should remove ngModel from you custom datepicker's .

Second, you are binding doInput() to (input), but it will fire only if you type in your input field, same for (change). You should bind to (bsValueChange) that's an output event exposed by BsDatepicker and it's safer, unless you plan to update value on user's input.

The resulting template will look like this:

You can probably use the techniques described here: Insert variable into global namespace from within a function?

I'd imagine it will require some bookkeeping in the __enter__ and __exit__ functions in order to clean up after itself. This isn't really something standard, so there my be some other foot-guns that I'm overlooking.