☒ Glad you got it. The Stripe API does communicate back like an object which seems to be something like an OpenStruct, so that's why I went that route.

 ☒ Yes, generally that is a good practice with the environment variables. However, I've found in this particular case with the parallel workers, that it also causes reporting issues with simple_cov, so typically, I comment out that line. I have my CI/CD create an artifact of the simple_cov report, so I like keeping it around  😊

That's strange. For the debugger, can you right click on the breakpoint column and try adding a conditional breakpoint there?

For the test explorer, what test framework are you using? You may want to try to go into the config and run the test manually. Also, since VS Code is an electron based application, you can pull up the debugger tools (similar to what is available in Chrome) and see any console outputs. There could be an issue and you'll get, hopefully, a more descriptive output.

 ☒ You could add it to the regular assets. I prefer to add any external sources to a separate place. You could put them in a vendor folder within the regular assets. Just having that bit of separation is nice because it's a reminder that we shouldn't ever manually change these files as upgrading to a newer version of the theme would "undo" our changes.

 ☒ Technically yes. However, since these permissions are highly derivative based on the application code, it doesn't make much sense to have it in the database. For example, if you add a new attribute to a user model, there will be a database change for sure, but also there will be application code change to consume this new attribute. It makes sense to keep the permission list with the code since that's where it is ultimately tied to.