Hi all, I've just installed a local version of Bolt 3 as I used to like working with Bolt 2 and wanted to check out the extension development workflow for the new version. The old method with building your extension initially as a local extensions used to be pretty straightforward, in that you could develop your extensions within the Bolt environment so you could immediately run the extension, check for errors, see what kind of error messages you were getting, fix them and so on.
I've just been checking out the workflow described in the docs for 3.3 and it seems to have removed local extensions and made developing in-situ very difficult. From reading the guidelines in the docs, you're supposed to write all your code outside of the Bolt environment (by guessing whether it will work?) then push it to a VCS repo and update the files within your Bolt test environment using composer, then check for errors etc.
This seems quite inefficient and unfriendly towards people who may not know the Bolt ecosystem fluently enough to get everything right without some trial-and-error, so I wondered if I'd misunderstood the docs and there is still a good way to develop in-situ.