Caleb Cushing

I think this might work for my use case #1456, but I'm not certain what the exact syntax would look like reading this issue.

yes, passing secrets via arguments or env vars is bad. Honestly I think just accepting them from a pipe would be good, or being able to pass filenames --user-file --password-file,...

hmm... I wonder if this is the same as the problem I just came here to report

I don't get an error though, mine just silently doesn't apply

linked my bug, seems very related to both that you mentioned, but mine seems to be both of the problems at once...

Yeah but that's a lot of duplicate code, which is why I'm saying that it would be better to do the tolerate private approach. Also if I did it in...

for mine, that's more or less what I'm doing now. The new command would be ``` yarn workspaces foreach npm publish --tolerate-private --tolerate-republish ``` which also has the benefit of...

I more or less agree with @sbrannen about SpEL, though I can also see why that would be hard to implement. However, maybe there's a way to register a plugin...

seriously? I mean, how does someone who can't figure it out, write the documentation on how to figure it out? oh I suppose I could go source diving. I too...

actually that last code doesn't work, I haven't found anything that actually does compile for this... even this. ``` }).getOrElseThrow( t -> Utils.exception( t ) ); ``` ```java static Exception...