Create an official Fig plugin and a oh-my-posh theme for sfdx/sf

[AllanOricil]

@mshanemc @cromwellryan

obs: fig.io doesn't have a Windows version yet: https://fig.io/user-manual/windows

Now that Fig is free for everyone, I believe it would be nice if Salesforce could develop and maintain an official Fig plugin.
I found this one https://github.com/wadewegner/salesforce-cli-zsh-completion but it is outdated.
Oclif could maybe have a "fig.io" generator plugin, so that all CLIs built with it could automatically generate fig packages (Heroku, for instance). There could exist a new flag in oclif build command to output a fig package as well. During oclif builds, a fig plugin is generated and added to the root of the project.

Look how cool the terminal becomes

Screen.Recording.2023-10-07.at.17.41.09.mov

Enhanced cd plugin! 🥹

You could also create a custom theme for Oh-my-posh that displays the default "org alias", and "group", the cli is configured with. This theme would display this information before the git branch

user > cwd -> (sf logo) org alias -> group -> branch

This theme can be activated automatically when opening projects with "sfdx-project.json" in the cwd

Look an example where the theme displays the Node version my project is currently configured to. The theme fetches this information from the project and then displays it if available. We could do the same in sfdx!

[cristiand391]

I've haven't tried fig yet but they have official oclif plugin:
https://github.com/withfig/oclif-plugin

have you tried it? I'm not sure if it still works (last commit was from ~2y ago).

[AllanOricil]

I have not. I see that it depends on oclif@v1, so maybe it no longer works. I will try and tell u later.

[AllanOricil]

@cristiand391

I think this should somehow be part of oclif because when installing a sfdx plugin it will be necessary to recreate fig specs to include new commands.

onPluginInstalled((plugin) => //generate fig spec))

I just realized that you can't rely on plugin developers to create fig specs for their plugins. It must be generated by the core package to enforce it on all plugins.

It would be good if clis built with oclif could opt in|out to generate fig specs in case they don't want it.

End user could also generate fig specs in case the cli owner opted to not do so running a command like:

my_cli fig setup

[AllanOricil]

🥺

[cristiand391]

I don't think this is sf-specific, following from your last comment:

I just realized that you can't rely on plugin developers to create fig specs for their plugins. It must be generated by the core package to enforce it on all plugins.

What we would need is support for plugins:postinstall and plugins:postuninstall hooks in plugin-plugins, then the oclif-fig plugin could re-generate use that to always update the fig specs.