arg.js | Lightweight URL argument and parameter parser

So I answer my own question. I deinstalled npm and node completely. I done it with this tutorial:

To completely uninstall node + npm is to do the following:

go to /usr/local/lib and delete any node and node_modules go to /usr/local/include and delete any node and node_modules directory if you installed with brew install node, then run brew uninstall node in your terminal check your Home directory for any local or lib or include folders, and delete any node or node_modules from there go to /usr/local/bin and delete any node executable

Than I installed npm with this line of code:

This works when REST argument is defined as @Args({ name: 'ids', type: () => [String] }) ids: String[]. Below is how the mutation resolver looks like.

Since you already define the mount_path='/data/storage' I don't think it's necessary to add sub_path='storage'. We can see it both in the docstring provided in here as well as the example provided in here.

I'm not sure what you trying to do and why you need an "event render" for it, but the "React way" is conditional rendering a component.

Mutating the DOM (like appending child) is an anti-pattern, as it's React's responsibility.

@user9964622, As a starting point below code can be used, it should be optimized further by CSS and your code:

Write a function to get day name:

the simplest way to hide previous events is by making use of the validRange setting such that it always starts the valid range at the current date. You don't need to provide an end date if you don't want to.

As discussed in the comments above, there is no single element in the fullCalendar HTML which represents a specific "cell" or "slot" in the timeGrid view. The grid you can see on screen is actually an illusion created by layering multiple tables on top of each other.

So to meet your requirement for a user to be able to select a 20-minute appointment in a free slot, I can see two main options. The first is what I would normally recommend, using the standard fullCalendar functionality. The second is more like what you are asking for, but I think it over-complicates things.

1) This option simply sets the calendar with a slot duration of 20 minutes, and then has code to stop the user from selecting a longer period of time (they cannot select a shorter period, due to the slotDuration setting. This means that they can click on any empty space once and it will know to create an event of the correct length in that location. The user is not allowed to select any slot where an event already exists. (P.S. I expect in reality you will need to collect more data before adding events, but for the demonstration it adds an event instantly.)

It turns out that you just have to add an extra -- on the end of print_b, which will tell npm to pass whatever arguments print_b got to print_a. So,

You are not handling error in "recover", that's a strange pattern imo, anyway it's better to not wrap promises like you did, and chain more "vertically" like this :