fullcalendar | quick hack to use FullCalendar | Calendar library

First, this error message is indeed expected on Jan. 11th, 2022.
See "Improving Git protocol security on GitHub".

January 11, 2022 Final brownout.

This is the full brownout period where we’ll temporarily stop accepting the deprecated key and signature types, ciphers, and MACs, and the unencrypted Git protocol.
This will help clients discover any lingering use of older keys or old URLs.

Second, check your package.json dependencies for any git:// URL, as in this example, fixed in this PR.

As noted by Jörg W Mittag:

There was a 4-month warning.
The entire Internet has been moving away from unauthenticated, unencrypted protocols for a decade, it's not like this is a huge surprise.

Personally, I consider it less an "issue" and more "detecting unmaintained dependencies".

Plus, this is still only the brownout period, so the protocol will only be disabled for a short period of time, allowing developers to discover the problem.

The permanent shutdown is not until March 15th.

As in actions/checkout issue 14, you can add as a first step:

You can use the answer at https://stackoverflow.com/a/29993265/5947043 and adapt it very slightly just to read the values from the checked checkboxes instead of from a dropdown list:

Use onchange event

You can use eventDidMount

This is how I implemented mine:

It doesn't send the first date of the month, it sends the first date which is visible in the view, so that nothing is omitted. For February 2022 for example, as per your screneshot, the first visible date is 30th January. Same with the end date.

However if you set the showNonCurrentDates option to false:

I just solve this issue by correcting the RxJS version to 7.4.0. I hope this can solve others issue as well.

You seem to be using Windows cmd to run the command, and hence you are getting the error.

The command:

You said you wanted to enable

users to drag and drop events within the calendar

But, as per the fullCalendar documentation, the droppable option...

Determines if external draggable elements or events from other calendars can be dropped onto the calendar.

(my bold).

What you need to set instead is the editable option, which...

Determines whether the events on the calendar can be modified. This determines if the events can be dragged and resized.

(again, my bold).

So if you set

Update: As pointed out in the comments (thanks @ADyson), your JS is referencing Fullcalendar v3. That's quite old now, v5 is current. My original answer referenced v5 docs, I've updated with v3 links/options as well.

Here's a super simple example. Notes:

• If you don't specify an initialDate (v5), (or defaultDate in v3) it will default to the current date - so no need to set up the current date.

• If you configure a JSON feed for events:, Fullcalendar will use GET to request them. If you want to use POST, you can do that, using the eventSources extended format (v5) (or v3). However, convention is that POST is for changing data (eg making a purchase, updating a record), while GET is for reading data. AFAICT you're just loading event data, which should really be a GET. I'd suggest sticking with convention and updating your back end to respond to GET instead of POST.

• Fullcalendar will automatically make a new request to your event feed when it needs new data, eg when you navigate to a new month. No need to add any code to manually handle that.

JS (v5):