autobahnswift / autobahn Goto Github PK

We need to get the homebrew tap formula up for autobahn and decide where we want to store the AutobahnDescription lib to link when we run the Autobahn.swift file

It would be really useful to have the power to import highways from another repo, such as:
https://docs.fastlane.tools/advanced/#importing-another-fastfile

We need an easy way to access ENV variables in the Autobahn.swift and it would also be nice to add support for loading variables from dotenv files as well. I believe if we load them in the CLI the process that gets kicked off to run the Autobahn.swift will share the same ENV but this still needs to be confirmed

Anyone here ??

One of the most useful features imo of fastlane is the plugin architecture. Everyone can just write his own plugin which is then loaded into fastlane and can be used.
We should think about this architecture as soon as possible since it's necessary for every feature development. Shuttle e.g. is 'just' an plugin for Autobahn which should be loaded explicitly when needed.
In contrast to fastlane, Autobahn is compiled instead of interpreted and plugins would be libraries instead of globally installed programs.

Some of the first thoughts that came to my mind:

• libraries need to be linked when the Autobahn.swift file is evaluated
  • currently only AutobahnDescription is linked, that needs to be extended
  • we could parse the import statements to get every library that is needed and try to link them - but we still need to specify where those libraries are located
• we need a protocol or base class for plugins, depending on the state and functionality the plugins need to provide
• we need a place for documentation
  • documentation should be shown when autobahn action foo is executed, so the CLI tool somehow needs access to the plugin + it's documentation

Maybe it makes sense to create an .autobahn directory in the root of the project. We could store plugin frameworks there to be able to link them. We could also search in that directory for available plugins that are shown when autobahn actions is executed.
It would then also makes sense to have a light package manager built in or use SPM somehow. (Maybe create a dummy package that has all necessary plugins + versions as dependencies.)