now.sh | Pipeable bash script that prints current time | Command Line Interface library

Against all recommendations you could:

The result you are getting is normal, the problem is that you are not performing Domain-Wide Delegation correctly. I come to this conclusion because of the following scenarios:

1. Calendar Id: john@example.com. If the service account has not impressed the user, it is expected that the user's calendar will not be found.

2. Calendar Id: primary. If the primary calendar of the service account does not have any events, it is expected that the list method does not return any results.

Comparing your code with the one in the documentation, I don't see where you place config.Subject = userEmail, as @DalmTo says. Try the following code to create the calendar service:

From what I can tell, redux will notify all subscribers to the store when anything in the store changes no matter if it's a subscription to a deeply nested leaf or a subscription to the top level of the state.

Yes, all subscribers are notified. But notice the difference between Redux and its React-Redux utils.

You could end up with lots of listeners and potentially performance issues?

With React-Redux you subscribe to a store (of Redux) by having a selector (useSelector/connect).

By default, every subscribed component in React-Redux will be rerendered if its subscribed store portion changed, to handle it you pass a selector which bailout the renders.

But for Redux:

• The notification itself handled by Redux (outside React).
• Redux doesn't handle the "deeply nested leaf" (React Context API handles it as part of React-Redux implementation) it doesn't handle locations - it just calling callbacks.
• The notifications are batched in a while loop outside the React context (optimized).

These errors were simply due to the packages being obsolete for your OS.

Just update them by running,

npm update --force

This will install the latest versions of these packages. This will take a while depending on your internet connection.

Then run npm start and it works.

I solved it. The problem was in SomeComponent.jsx.

Solution:

1. Delete

First of all, you need to review carefully the difference between tabindex=0 and tabindex=-1. Setting tabindex=0 means that the element is focusable, both manually with tab key and automatically via script. Setting element to tabindex=-1 means that only a script can set focus on it, while it isn't possible to focus the element manually.

Knowing this, you should understand what you did wrong. The most obvious solution would be to focus the element with tabindex=-1 when your modal is shown. If for any reason it's much more logical to have the element with tabindex=0 focused when the modal is opened, then you may first focus the element with tabindex=-1, wait for a short while (50-100ms), and then focus the element with tabindex=0.

Concerning scroll, normally, focusing any element (with whatever tabindex or none) should automatically bring it into view it it isn't yet visible, but if is already visible then the scroll shouldn't change. So even by focusing the element with tabindex=-1 and then the one with tabindex=0, the element with tabindex=-1 should stay visible.

The Black code style was the right place to check and you are right, it's not super clear for this use-case. I can say if you don't split the string of the value into two strings then Black will put it on one line which you may prefer. I'm not sure Black has a good way to know when it can concatenate 2 strings to one when it makes sense - see discussion here.

e.g

If I understand this right you saying that for shapes which are added individually there is an easy 'undo' process, but for lines which use an array of points for their segments, there is no simple undo - and no code in the tutorial you are following?

I can't give you a react code sample but I can explain some of the concepts you need to code up.

The 'freehand line' in your whiteboard is created as a sequence of points. You mousedown and the first point is noted, then you move the mouse and on each movemove event that fires the current mouse position is added to the end of the array. By the time you complete the line and mouseup fires, you have thrown multiple points into the line array.

In the Konvajs line tutorial it states:

To define the path of the line you should use points property. If you have three points with x and y coordinates you should define points property as: [x1, y1, x2, y2, x3, y3].

[Because...] Flat array of numbers should work faster and use less memory than array of objects.

So - your line points are added as separate values into the line.points array.

Now lets think about undo - you are probably there already but I'll write it out anyway - to undo a single segment of the line you need to erase the last 2 entries in the array. To erase the entire line - well you can use the standard shape.remove() or shape.destroy() methods.

In the following snippet the two buttons link to code to 'undo' lines. The 'Undo by segment' button shows how to pop the last two entries in the line.points array to remove a segment of the line, and the 'Undo by line' button removes entire lines. This is not a react example specifically, but you will in the end create something very close to this in your react case.

After going over the FAQs. I found an entry named Unmatched Function Pattern, it states:

the functions property uses a glob pattern for each key. This pattern must match Serverless Function source files within the api directory.

It also mentions:

if you'd like to use a Serverless Function that isn't written with Node.js in combination with Next.js, you can place it in the api directory (provided by the platform), since pages/api (provided by Next.js) only supports JavaScript.

I think that this needs to be clarified a bit. There is indeed an default api folder when you bootstrap a Next.js project with create-next-app, but it's created inside the pages directory.

If you follow the example they give, you might just go ahead and create a serverless function in a supported language (other than JavaScript) inside the pages/api directory and wonder why Vercel doesn't pick it up when you deploy.

In short, if you're using another language to write a serverless function inside a Next.js project. Be sure to place it inside an api folder that sits in the root directory of the project (if there's none, create one).

Thanks to @evgenifotia for the suggestion, it pointed me in the right direction and helped me solve this issue.

Note: You can only have a single api directory that houses serverless functions. Either you have a pages/api directory or a api directory in the root folder, having both in a single project is not supported.