Anthony Lawn

Sure thing: it's the one in the docs [here](https://vitest.dev/guide/debugging.html).

I was looking at this FR and it interested me (moreso for custom maps to use, than for crafting CPUs to drop), and I think I could implement it fairly...

I think using json schema would make a lot of sense. I think, considering how many people are looking to remove first/last name from users, it'd be prudent to get...

So here's an example of what the default user schema might look like. I also added a `primaryKey: "email"`, which could in theory be a way to define unique users...

Oh, that's a great idea. I was thinking admins might want to remove one of the password or externalAuth fields if they know they'll never use them, but that was...

That idea looks good to me! It sounds easier to implement, solves the issues I left to be worked out, and would already have an interface in the console.

That issue is asking for something different, actually. That issue is asking for triggers based on updating, or deleting users - which is also something I need, so I've subscribed...

I looked into implementing this myself a bit, and I think it's feasible by appending it to the fields passed to ctx.v1 in `runPostExternalAuthenticationActions` when the flow is the external...

I'd be willing to do any testing. Unfortunately, I don't see a makefile anywhere. I was able to run the bash script available in the v0.3-beta linux release, but obviously...

I'm having issues compiling. There was an issue with liblastfm when using qmake, realized I needed to run bootstrap, but that didn't fix it. Downloaded the src directly from the...