Skip to main content

Metro App - Call a Java Script method by name and send the list of params

In a Metro App that I writing in Java Script I wanted to call a function based on the method name that is send as a string. In C# we would need to use reflection but Java Script doesn’t require this think. We can very easily iterate through all the method like in an array and call our method.
obj[“”methodName ]();
obj[“”methodName ](param1, param2, …);
The above example get our method using “[…]” and after that calls our method. This is quite simple and a powerful feature.
But how we should rewrite this code if the parameters list are specified as an array. We want to be able to dynamically call any method and give a list of parameters as an array. If we try something like this:
var params = [param1 , param2];
obj[“”methodName ](params);
we will see that is not working, actually we set only the first parameter as an array, and the rest of parameters will be ‘undefined’. What should we do in this case is to use the apply method. Basically this method permits to specify the list of parameters as an array.
var params = [param1 , param2];
obj[“methodName”].apply(obj, params);
The first parameter need to be object of which the function is called. The second parameter is our array list. We can find another similar method named “call” that do the same think but without specifying the list of parameters (the function don’t have any parameter), but each parameter separately . The next 3 examples are equivalent for a function that doesn’t have any parameters:
obj[“methodName”].apply(obj);
obj[“methodName”].call(obj);
obj[“methodName”].();
or
obj[“methodName”].apply(obj, [param1]);
obj[“methodName”].call(obj, param1);
obj[“methodName”].(param1);
What we achieved? We are able to call dynamically any Java Script method based on a string name and an array of parameters.

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

Azure Service Bus - How to extend the lock of a message | RenewLock

In this post we will discuss about Azure Service Bus Topics and Queues, with a special focus on Peek and Lock feature. Introduction Azure Service Bus is a messaging system that allows us to send messages between different systems in a reliable and easy way. A lot of concepts from ESB are implemented by Service Bus, allowing us to do do magic stuff with messages. There are two ways to consume messages from Service Bus Peek and Lock - locks a message for a specific time internal and notify Service Bus when we want to mark the message as processed (removed from Service Bus) Receive and Delete  - once a message is received from Service Bus, it is also deleted automatically from the messaging system Peek and Lock When using Peek and Lock, by default we lock the message for 60 seconds. This means that in this time interval the message is not available/visible for other consumers. Once we process the message we can mark it as processed. If we don't mark the message as processe...