api-design | API Design & Security | REST library

I implement an auth endpoint which takes an email and password and returns a JWT token. Inside the JWT there is a payload containing the user ID. Does it matter from a REST/JWT standards perspective which of these approaches I take?

1. return the token and let the client request the /users/user_id resource on a callback with the decoded user_id and the token
2. return the entire user object with the token from the /auth endpoint for the convenience of the client.

(my question is implementation/library agnostic and about the api-design pattern)

In Trio, if you want to write some data to a TCP socket then the obvious choice is send_all:

I have been looking through reddit and n have tried the solutions in the following links but have not worked. E11000 duplicate key error index in mongodb mongoose

Basically I have a list schema and a user schema and I want to index to have a user and a list name associated with it. Here is my list schema:

I created some projects in google apps script in the past for some automation, that also included some http-fetches. In the past, this worked with .fetch() pretty well, but now we need to fetch multiple urls. Since apps script now uses V8 runtime I considered to do so with promises. I'm also quite new to async/await and promises in general. So I considered to try the UrlfetchApp.fetch() within async functions, just to find out, that there's no difference in execution time.

I red, that UrlfetchApp.fetch() will always be sync, no matter whether you declare your function as async or not, due to the GAS-API-design. But I can't find detailed infos on this. Is this true?

If yes: Then the only way to fetch multiple urls would be UrlfetchApp.fetchAll(), right?

If no: Means simple .fetch() would work inside async funcs (and could be chained in Promise.all()) then I'd invest further time in this.

So, yes or no would help a lot here!

Thanks in advance!

I am trying to create an API for user authentication to access data from SQL Server, however most resources I have found are based on MongoDB, such as this one: Restful API design with Node.js

I followed the tutorial and can connect to SQL Server by replacing 'mongoose' with 'mssql'.

Now there is a part that I can't figure out how to change it to the equivalent code:

There are many other questions here which target the same problem many-to-many relationship url design for restful apis. I have somewhat the same, but it differs from other.
I couldn't find any better approach.

I have locations resource, and services resource`

Imagine I have an endpoint on a REST API that only supports these sort parameters: date and price. How should I react to an API call that asks data sorted by tax-rate?

For a filter param it's a no brainer, I return empty list. but should I do the same for a sort param or simply ignore the invalid sort param and return the data based other other parameters?

I know in some cases there's no strict answer to API-design questions, I'm curious to know which approach supports a wider range of use-cases.

I am using a bunch of synchron functions from my own "old" libary. These are used to backup files, compress them and upload them per example. For further use i would like to change these to async functions. Please forgive me my following long intro, but the problem needs a bit background..

i have found several information on how to convert this:

A great book : Concurrency in C# Cookbook from Stephen Cleary.

Here is example Pattern i am tryping to adept:

• https://docs.microsoft.com/en-us/dotnet/standard/asynchronous-programming-patterns/interop-with-other-asynchronous-patterns-and-types#EAP

Also some posts here:

• C#: HttpClient, File upload progress when uploading multiple file as MultipartFormDataContent

• System.Net.Http.HttpClient.PostAsync blocks and never returns

• Library Design Guide

Main Points:

• Use Async /Await all the way done
• Don't wrap synchron Methods in asychron pattern with result or wait. Use await everywhere possible
• Wrap EAP Pattern Methods to Tasks
• Avoid Using Task.Run in Libaries
• Use ConfigureAwait(False) in Libaries
• Use Task.Run instead in your UI
• Use IProgress to post progress

My basic class looks like this:

I'm working with a Java API now converted into multiplatform Kotlin. It used to use java.lang.Optional as the return type of many calls. I understand this is not the idiomatic Kotlin-way (see discussion) but this is an existing API, Optional stays (also it isn't a bad choice for the Java-facing client). My question is how?

Note: The code only needs to return Optional.of(x) or return Optional.empty() to the external API. Any internal uses will be purged.

• How do we use expect/actual/typealias to use the real Optional class when available?
• Is there a way to avoid re-implementing a fake Optional class on non-Java targets (i.e. work idiomatically with nullable? suffix)