Skip to main content

JavaScript: Next Unique ID Function

Unique ID generation is used in JavaScript application in many places. For example giving the unique id to DOM element or may be using it to some data structure for storing in memory, where it can be use latter.

Most of the implementation I see is just defining the integer and increasing it on every call. But it is potentially candidate to integer overflow issue, which can cause errors in many edge case scenario.

var nextUid = (function(){
  var idCounter = 0; //integer counter
  return function (prefix) {
     //counter increment on every call, and it can run into integer overflow issue
     var id = ++idCounter; 
     return String(prefix == null ? '' : prefix) + id;

When I was reading through AngularJS source code, found this really good implementation of unique ID generation. Below is the extracted and updated version of the same, so you can use it independently.

 A consistent way of creating unique IDs in angular. The ID is a sequence of alpha numeric
 characters such as '012ABC'. The reason why we are not using simply a number counter is that
 the number string gets longer over time, and it can also overflow, where as the nextId
 will grow much slower, it is a string, and it will never overflow.
 @returns an unique alpha-numeric string
var nextUid = (function(){
  var uid = ['0','0','0'];
  return function() {
    var index = uid.length,

    while(index) {
      digit = uid[index].charCodeAt(0);
      if (digit == 57 /*'9'*/) {
        uid[index] = 'A';
        return uid.join('');
      if (digit == 90  /*'Z'*/) {
        uid[index] = 'a';
        return uid.join('');

      if (digit == 122 /*'z'*/) { 
        uid[index] = '0';
      } else {
        uid[index] = String.fromCharCode(digit + 1);
        return uid.join('');
    return uid.join('');

//output: "001", "002", "003", "008", "009", "00A", "00B", .., "01s", "01t", "01u", "01v" ..etc

Benefited of using this function is slow rate of increment, and you will never have to worry about the overflow issue. 


Popular posts from this blog

ERROR: Ignored call to 'alert()'. The document is sandboxed, and the 'allow-modals' keyword is not set.

Recently I found this issue while writing code snippet in "JSFiddle". And after searching, found this was happening because of new feature added in "Chrome 46+". But at the same time Chrome doesn't have support for "allow-modals" property in "sandbox" attribute. Chromium issue for above behavior: To make it work you have to add "allow-scripts allow-modals" in "sandbox" attribute, and use "window.alert" instead of "alert". <!-- Sandbox frame will execute javascript and show modal dialogs --> <iframe sandbox="allow-scripts allow-modals" src="iframe.html"> </iframe> Feature added: Block modal dialog inside a sandboxed iframe. Link: Feature working Demo page:

Application Design Notes

Don’t be afraid to write your own code, but be absolutely sure you need to Don't reinvent the wheel Learn more about your libraries and take full advantage  Date time calculation is hard ( leap second ,  leap year ), use trusted library  js-joda ,  momentJs ,  joda (java) Simple is better than perfect (nearly) every time If you can deliver a sub-optimal solution (that solves the problem but has known limitation) in a week instead of a full featured one in a month DO, IT Simple system are Easy to reason about  Easy to debug Easy to refactor Easy to learn Simple doesn't mean you skip good engineering, but you can use duct tape. Build things the right way from the start, refactoring is hard and expensive Security Manage and store passwords securely Telemetry Common retrofitting "grunt work" Internationalization + localization Web Content Accessibility Factoring and styling HTML UI Adding unit test to an existing codebase LOG LOG LOG Log, but do it right We spend lot of t

How to store user password at server!!!

Trick is, you should never store user password… never ever. Now the real question is, then how to authenticate and authorize the user with password. And answer is when user enter the password, we should encrypt the password and store the hints. So next time when user enter the password we follow the same process and compare hints, if both hints are same then password is matched, else it is wrong password. Next question will be, what kind of hints, and how to generate these hints. In simple term hints are the obfuscated and fragmented form of user password. And very important part is hints generation process, which have to be collision resistant , means there will be very less possibility to find the data which generate same hints (like Cryptographic hashing functions ). Below is the simple checklist of password hashing and storing, which you should always keep in mind. PS You're Probably Storing Passwords Incorrectly Storing Passwords - done rig