Also thinking of adding an lastUpdated property to the Plugin struct to track the last time the binary was built.

Nice addition, I was thinking of something like this because with the hook addition we need to show what the plugin is actually doing.

The current implementation breaks a little bit the concept of a list, because a plugin description takes multiple lines. For instance if my project has 2 plugins configured, the output of ignite plugin list is :

$ ignite plugin list
	ℹ️ example-plugin info
Path 						Status 		
/home/tom/src/ignite/plugins/plugin-example 	✅ Loaded 	

	💻 Commands
Use 		Under 	
ipfs 		ignite 	
shutdown 	ipfs 	

	🪝 Hooks
Name 		On Command 		
my-hook-serve 	ignite chain serve 	
my-hook-build 	ignite chain build 	

	ℹ️ my-new-plugin info
Path 						Status 		
/home/tom/src/ignite/plugins/my-new-plugin 	✅ Loaded 	

	💻 Commands
Use 		Under 	
my-new-plugin 	ignite 	

	🪝 Hooks
Name 	On Command 	

I think we should keep the table format for plugin list, with a reduced set of information, for instance we could use the nice icons you added :

$ ignite plugin list
Path 						Status 		
/home/tom/src/ignite/plugins/plugin-example 	✅ Loaded 2🪝 1💻 	
/home/tom/src/ignite/plugins/my-new-plugin 	✅ Loaded 1💻 	

Then to have the complete description, we need to add a new command ignite plugin describe <pluginPath> that would output everything like you did but for a single plugin.

WDYT?

I think this is a good path forward, I originally isolated the hooks and cmd table under respective flags. but I like this better. I will move the command and hook info to ignite plugin describe <pluginPath>

when I merged main into this branch there were suddenly many more file changes. tried to revert the merge of main but can't seem to get an accurate delta count

@joshLong145 I can't explain what happened, this is confusing. Probably related to the multiple merge between develop and rebase on main.

I think the best way to fix this is to rewrite the history. I was able to have the correct diff (I think) with the following commands from your branch :

$ git diff main -- ignite/cmd/plugin.go > ../plugin-list.patch  # create a patch that contains only the diff that we are interested in
$ git reset --hard main
$ git apply ../plugin-list.patch

Check if the diff is now correct (git diff main), and if you're agree with it, and if nothing is missing, commit and push force into your branch.

@tbruyelle @aljo242 I've reworked plugin list and plugin describe to use an instance of session let me know what you think. if this is not desired ill revert the commit.