Creating a Promise

Share This Post

Promises are used for asynchronous code. It is a temporary holder for a value that gets returned by an asynchronous call. For example, a call to a web service might use a promise. You can call the web service with a promise and once it is fulfilled, you can run some code. Here is the syntax…

let myPromise = new Promise(
    function(resolve, reject){
        setTimeout(resolve, 1000, ‘a value’);
    }
);
console.log(myPromise); 

Here we are creating a promise. Within the promise method, we have an anonymous function that is making the promise call. In here is where you might find a call to a web service. In our example, we are simply running a setTimeout function to simulate a call to a service that might take a second. Notice the two parameters in the function…resolve and reject. Those are the two things that can happen to a promise. It can be rejected. We can then handle the rejection, or it can be resolved (fulfilled). This settles the promise and we can programmatically handle the response.

In our code, you should see the promise logged to the console. It is in a pending state because we haven’t settled it. We haven’t done anything with it yet. Feel free to change the resolve to reject in the setTimeout to see the difference.

Happy Coding!

Clay Hess

More To Explore

Code

Demystifying Scrum User Stories Confirmation: Ensuring Quality and Collaboration

One of the key elements of Scrum is the use of user stories to define the requirements of a system or feature from the perspective of the end user. As teams work through the product backlog, it becomes crucial to confirm the user stories to ensure they meet the desired criteria and are ready for development. In this blog post, we’ll explore the concept of Scrum user stories confirmation and its significance in delivering high-quality products.

Code

The Power of Conversations in Scrum User Stories

At the heart of Scrum lies the concept of user stories, which serve as a means of capturing requirements from the perspective of end-users. However, the true power of user stories lies not just in their written form but also in the conversations that take place around them. In this blog post, we will explore the significance of conversations in Scrum user stories and how they contribute to the success of Agile projects.

Do You Want To Boost Your Business?

drop us a line and keep in touch

Scroll to Top
small_c_popup.png

Need help?

Let's have a chat...


Login

Jump Back In!

Here at Webolution Designs, we love to learn. This includes sharing things we have learned with you. 

Register

Begin Your Learning Journey Today!

Come back inside to continue your learning journey.