Derek F

tag v2.0 for breaking backwards compatibility 👍 If this gets approved, then for anyone that relied on `$ZSH` in there addons: ```sh git grep 'ZSH' ```

### Pros for `.zprofile` > the two are not intended to be used together, although this could certainly be done if desired - My intent was to not be exclusive...

Yeah don't worry. I'm no expert either. Thanks for reviewing!

I think I'd rather just remove the wildcard prefix feature. It is an overcomplication. 1. **zshenv** - ~`**/*path.zsh`~ `**/path.zsh` - ~`**/*env.zsh`~ `**/env.zsh` 1. **zprofile** - ~`**/*profile.zsh`~ `**/profile.zsh` 1. **zshrc** -...

I was able to get around this by setting `Meta.additional` and `Meta.load_only`: ```python import dataclasses as dc import marshmallow as mm import marshmallow_dataclass as mmdc @mmdc.dataclass class Dog: name: str...

Ah, didn't notice the `attribute` argument. Thanks for pointing it out. Perhaps an explicit mention of overriding the primary key could be added in the docs? #### Basically my use...

Perhaps you could give it a 1.0 release to ease our minds :innocent:

Despite the hooks being similarly designed to be tied to their respective Helm commands, it is counterintuitive that a rollback defaults to using the target release instead of the source...

# Workaround Found success with this workaround: ```xsh @aliases.register("xuv") def _xonsh_uv(args: list[str]): $UV_PYTHON=@(__xonsh__.imp.sys.executable) uv @(args) ```

I like that design -- especially because it remains consistent with the different tuple types supported by [Callable Aliases](https://xon.sh/tutorial.html#callable-aliases). I'll look into getting a PR going for this today as...