common Exporting common util

[mtuchi]

Summary

Fixes namespacing of util functions in common and exports the utils properly for use by other adaptors.

AI Usage

Please disclose how you've used AI in this work (it's cool, we just want to know!):

• Code generation (copilot but not intellisense)
• Learning or fact checking
• Strategy / design
• Optimisation / refactoring
• Translation / spellchecking / doc gen
• Other
• I have not used AI

You can read more details in our Responsible AI Policy

[josephjclark]

Alright - the problems here are all do with how our docs generator decides the namespace for a given function. It's a very rigid and limiting system at the moment which just uses the filename and assumes that's it.

I'll add a jsdoc extension to give us more control over this

[josephjclark]

@mtuchi this should now be working

I've tested with this job:

fn(state => {
  const formatted = dateFns.format(new Date(), 'yyyy');
  console.log(formatted);

  return state;
});

http.get('https://jsonplaceholder.typicode.com/todos/1').then(state => {
  console.log(state);
  return state;
});

fn(state => {
  console.log('testing util namespace ');
  const a = util.encode('xxx');
  console.log(a);
  const b = util.decode(a);
  console.log(b);

  console.log(util.uuid());

  return state;
});

[josephjclark]

And I've added a section to the Wiki for this: https://github.com/OpenFn/adaptors/wiki/Adaptor-Writing-Best-Practice-&-Common-Patterns#namespacing

[mtuchi]

Hiya @josephjclark i have tested this PR everything looks good ✅ , Before you merge can you take a look at this PR #888
it's just a cleanup on http adaptor on exporting util function properly. I have used common-helpers as the base branch