A quick tip here for new-to-XCode iOS developers.

If you want your iOS app to only display in portrait (or landscape) modes to users when they are using your app, there's a little trick to get it to apply to both iPhones and iPads.

It would appear obvious at first that this should work:

![XCode-orientation-settings](/assets/screen-shot-2021-07-17-at-8.38.02-pm.jpg "XCode Orientation Settings")

Select both device types and select portrait as the only option, but no, this does not work for iPads.

What you actually need to do is:

1. Uncheck the iPhone checkbox in the General → Deployment Info section
2. Ensure iPad is checked
3. Set Device Orientation checkbox for Portrait only true
4. Set the Requires full-screen checkbox to true
5. Build/Run the app to confirm

You'll most likely see after step 1 is completed that the orientation options defaults back to both portrait and one of the landscape options.

A quick how-to for setting portrait (or landscape) only for your iOS app for iPads as the default setting in XCode doesn't apply to all devices equally.

Setting iOS App to Portrait Only for iPads

## What is Bun?

B﻿un is a new Javascript runtime that focuses on simplicity, performance and developer experience. It has been built with the lessons from NodeJs in mind to minimise some of the common pitfalls of a Javascript runtime.\
B﻿un has been built to minimise and abstract away a lot of the complexities from NodeJs to allow developers to focus on clean, maintainable, performant code.

## Getting Started

* I﻿nstall Bun for your OS as per the official Bun [instructions](https://bun.sh/docs/installation)
* C﻿reate a folder for your Bun project code files to live. 
* I﻿n a terminal for the new folder run `bun init` to set up the Bun project
* C﻿reate an app.ts file in the folder

## C﻿reating the Bun Application

O﻿pen the app.ts file in your code editor of choice and add the following code:

```typescript
const server = Bun.serve({
  port: 3000,
  fetch(request) {
    return new Response("Welcome to Bun!");
  },
});

console.log(`Listening on ${server.url}`);

```

I﻿f you are familiar with the Express framework, this should look very familiar.

T﻿his code snippet creates the bun app, sets up a basic response for the server, configures a port and starts the server.

## R﻿unning the Server

B﻿ack in your terminal with the project folder open, run `bun app.ts`

I﻿n a browser, you can now navigate to `http://localhost:3000` which will present you with the text 'Welcome to Bun!'

## C﻿onclusion

A﻿s shown above, the Bun framework provides a simple and effective way to create an HTTP server or API. This allows you to focus on writing clean, maintainable and performant code.

Bun is a lightweight and flexible framework for building HTTP servers and APIs in the mould of NodeJs. This post will guide you through the initial configuration set up of a Bun HTTP server.

Setting Up an HTTP Server with Bun


By default, a new Javascript/Typescript function created in an Azure functions app stringifies any data the function returns in the context.res object. 
This is because the default content-type header is text for all node.js functions in Azure.

The context.res object is generated by the Azure function runtime as a wrapper around the node runtime's default response object and contains all the information that is sent back to the client after the function executes.

Most of the data transfers do not require the data to be in a string format.

Simply adding this to the beginning of the specific function will always return the JSON object format instead:

```js
context.res.headers = { "Content-Type": "application/json" };
```

This forces the response header to the http request to have the json content type for the data.

So instead of having a response like this:

```js
context.res.body = '{"success": "true", "message":"Function ran successfully"}';
```

You will end up with:

```js
context.res.body = {
    success: true,
    message: "Function ran successfully"
};
```

Often, by default, an Azure Function written in NodeJs stringifies the response object being returned. This results in unnecessary JSON parsing on the client in order to be able to process the response. Luckily, we can avoid this by making a simple change to the Azure Function to ensure the object is returned.