teem | web tool and mobile app | Collaboration library

Refer to https://docs.microsoft.com/en-us/office/dev/add-ins/reference/manifest/extensionpoint to read about different extension points which are available on different surfaces in Outlook.

Specifically I think https://docs.microsoft.com/en-us/office/dev/add-ins/reference/manifest/extensionpoint#appointmentorganizercommandsurface would be of interest for you. This extension point makes your addin visible on Appointment compose surface.

As pointed out by others and me in the comments There are 2 syntax issues

1. Change articles?.name to articles.name in the keyExtractor
2. Destructure the props correctly in DetailScreen from (result) to ({result}) Both these are important for your code to work correctly.

Lastly, I noticed your articles data is an object {} while data in FlatList must be an array []. So please transform the article data you are receiving from the API into an array and it will work. Link to React Native official docs where you will see FlatList only accepts array in the data prop.

Here is the link to codesandbox where you will see I transformed your articles object data into updatedArticles array and passed the updatedArticles into the FlatList and it is rending it correctly.

While writing this answer, I've changed multiple things:

• Datalists do not return the value, the input does source.
• The document.getElementById('ori').value; was changed to orgi
• Got the .value from the elements
• Added to be able to use swal

It's not about nested http calls, it's about nested subscription which it's RxJS antipattern. RxJS is the library which solves problems reactively and declaratively. It means that your data flow in application should be described as streams. Good patterns in RxJS assume that entire flow should be written as one lazy loaded streams. In your case the entire flow is: fetch person with id=1 -> determine homeworld -> fetch homeworld. So you don't mind actually about person details, but about homeworld. Please notice, that in second case you don't call any http method, you only compose lazy stream. It allows to you use this stream in place or subscribe it in another place without storing state. This is huge advantage, that you don't care about state or intermediate state (imperative approach).

What's more, when you use .subscribe() you create subscription that should be managed in service/component lifecycle. If you create one stream flow, only one subscription is created, so subscription managing is just easier. I know, that http.get/post observable is completed after data is fetched, but what if you leave component where that http call was made? Code will execute side-effects in scope which doesn't exist.

I think very good explanation you will find also in https://medium.com/angular-in-depth/when-to-subscribe-a83332ae053

Do you mean using adist like below?

Just pick the output of reset function to a variable and use it in your insert statement.