Zach Daniel

👋🏻 Hello! The simplest thing to do would be to add an attribute with a question mark at the end, e.g `attribute :foo?, :boolean`. This should fail. Then we'd add...

There currently aren't any transformer specific tests, moreso integration tests on them running whenc compiling a resource. For example: https://github.com/ash-project/ash/blob/main/test/resource/attributes_test.exs Also great work! One thing we may want to do...

I'll close this issue for now, actually, since we've essentially decided not to do it.

I've had a thought on this, and I think that as long as these relationships are "read only" that it may actually be quite easy to work these out. They...

Currently there are "custom relationships", and "aggregates" to support some of these use cases. However, they aren't as fluid as the option to simply say things like `has_one :organization, Org,...

A proposed API for composing many patches to a project. This is very similar and inspired by the patterns that @msaraiva put forth with the code in surface. https://gist.github.com/zachdaniel/947bda4a8866725b5f5d118f237563b1

Wow! So it looks like you've already implemented practically exactly the proposed API! That is huge 🔥 🔥 🔥 My 2 cents is that that logic would be best served...

@NickNeck if you did extract that project modification toolchain to its own repo, I'd likely start using it in the next couple of weeks and would happily contribute. I'd likely...

🤔 I think perhaps we can just make formatting a configurable behavior, but realistically I can't imagine anyone doing what we're doing(rewriting source) without wanting at least the end result...

Yeah, I definitely think it makes sense to leave not formatting as an option to allow for cases where people care. I imagine it should relatively easily be added as...