Javascript Question posted in
A very good W3school tutorial can be found here.

javascript: string to object and dot notation

In the application I am working on, I have some configuration stored in a memo field in object literals.
enter image description here

 {
    JWT : { endpoint  :"https://somelink1",
               clientid     :"consent-management",
               grantType  :"client_credentials" },
    CMP : {endpoint      :"https://someotherlink2",
                contentType :"application/json"}
 }

Using regex and application specific javascript language, I am maching the object part only and parsing it

var auth    = nms.extAccount.load(39010);
var regex   = /{([^;]*)}/gm;
var authObj = JSON.parse(JSON.stringify(auth.comment.match(regex)));

logInfo(authObj);

enter image description here

Normaly I would then just use dot notation authObj.JWT.endpoint) to navigate through the object but it isnt working.

14/05/2024 13:25:47 js JST-310000 Error while compiling script 'WKF9/js' line 6: authObj.JWT is undefined.

Just wondering if I am missing something.

I log the type and is object

14/05/2024 14:24:32 js object

Tags:

3

Answers


  1. 0

    I believe the regex will match the first open curly brace (before JWT) up to the first closing brace (after "client_credentials").

    Perhaps you can just remove the "DO NOT CHANGE" part of the comment and then parse it:

    let authObj = JSON.parse(auth.comment.replace('***DO NOT CHANGE***', ''));

    or if that won’t work for every case, then the regex likely needs to be corrected to parse out the full JSON text.

    Login or Signup to reply.
  2. 0

    How about treating the config as string but sanitizing it towards a valid JSON-string by a simple replace task, where the following regex … /w+(?=s*:s*["{])/gm … does match each of the config’s keys.

    And in order to remove the asterisk suffixed/prefixed comment(s) another regex based … /s****.*?***s+/gm … replace task needs to be run before the parsing into an authorization object can be safely approached.

    Note

    Whereas the first introduced key-matching regex is already sufficient enough, another regex like … /(?<=[{,]s*)w+(?=s*:s*["{])/gm … is even more reliable. This lately introduced regex makes not only use of a positive lookahead like the former one, but also uses a positive lookbehind which might not be supported by some older JS-engines.

    const configString = `*** DO NOT CHANGE *** 

{
    JWT : { endpoint  :"https://somelink1",
               clientid     :"consent-management",
               grantType  :"client_credentials" },
    CMP : {endpoint      :"https://someotherlink2",
                contentType :"application/json"}
 }

*** DO NOT CHANGE ABOVE EITHER *** `;

const regXLiteralKey =
  // see ... [https://regex101.com/r/9Uejvk/1] ... positive lookahead only.
  /w+(?=s*:s*["{])/gm;

  // // see ... [https://regex101.com/r/9Uejvk/4] ... full positive lookaround.
  // /(?<=[{,]s*)w+(?=s*:s*["{])/gm;

const regXAsteriskComment =
  // see ... [https://regex101.com/r/9Uejvk/3]
  /s****.*?***s+/gm;

const authObj = JSON.parse(
  configString
    .replace(regXAsteriskComment, '')
    .replace(regXLiteralKey, '"$&"')
);

console.log({
  authObj
});
console.log('authObj.JWT.endpoint ...', authObj.JWT.endpoint);
    .as-console-wrapper { min-height: 100%!important; top: 0; }
    Login or Signup to reply.
  3. 0

    Just eval it in an arrow function if you trust the code:

     const auth = {comment:`
 
 DONT CHANGE
 
 {
    JWT : { endpoint  :"https://somelink1",
               clientid     :"consent-management",
               grantType  :"client_credentials" },
    CMP : {endpoint      :"https://someotherlink2",
                contentType :"application/json"}
 }`};
 
 
 const obj = (code => eval(`(${code})`))(auth.comment.replace(/^[^{]+/, ''));
 
 console.log(obj.JWT.endpoint);
    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search