Issue which needs to be solved: -

• If a user needs to add just a few staged files and commit them to the repository, the current pre-commit hook will become a problem as it will add back everything once the linting is done

Documentation for lint-staged - https://github.com/okonet/lint-staged

Refer the following blog for more information :- https://prettier.io/blog/2022/06/14/2.7.0.html

Example URI formats which can be accepted:-

• {{url}}/api/users?select[name]=true
• {{url}}/api/users?select[password]=false

Issue to be addressed :-

The default GITHUB_TOKEN does have permission to bypass branch protection rules and as such requires things such as approval before commiting due to which it fails inside the runner. This can be mitigated by using a personal access token with elevated permissions.

For more information refer the following docs - https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases

Details - rewrite the entire @sliit-foss/babel-plugin-transform-trace library as an esbuild plugin

Example URI formats which can be accepted:-

• {{url}}/api/users?populate[role]=true
• {{url}}/api/users?populate[role]=false
• {{url}}/api/users?populate[role]=1
• {{url}}/api/users?populate[role]=0

Currently @sliit-foss/functions needs to be installed separately in the client project for the build to work smoothly if using package managers like PNPM due to hoisting. This can be avoided if the required functions can be polyfilled in during the build process.

I'm not really sure of where to start on this, will have to inspect existing plugins which provide polyfills to get an idea on this

Requirement :- As a developer, rather than ignoring the functions which I do not need tracing for by specifying them in the babel config, it would be much more feasible to mark only those which needs to be traced with an annotation in the source code.

Example solution :-

@timekeeper
const foo = () => {
  console.log("Inside foo");
}

Note:- decorators are not natively supported in JavaScript, a plugin such as @babel/plugin-proposal-decorators will need to be incorporated

The goal is to achieve the native feel of an interactive CLI tool with support for a help command and input suggestions

Docs: -

• Commander.js
• Yargs

Refer the following documentation for more information on writing tests for babel plugins - https://github.com/jamiebuilds/babel-handbook/blob/master/translations/en/plugin-handbook.md#toc-unit-testing

Details - rewrite the entire @sliit-foss/babel-plugin-transform-trace library as a webpack plugin

Add support for log colorization a feature which is highly useful in displaying tracing logs in the timekeeper products