CheaterCodes

I've done some more thinking, here are some updates: ## Comparison to previous design Target application is analogous to the originally defined "read phase", or "reads". Transformer application is analogous...

After some internal discussions, this proposed change has been approved. Some additional details regarding the changes: - The function `targets..target` should be changed to that the return vaue is a...

I've done some more thinking, and I'm running into some walls that were build when originally designing this project. Here's my dilemma: Chasm was designed to sort transformers. Those transformers...

I definitely would go for the first approach. I would possibly even go further and restrict remapping to `.remap` files which can be valid json5 and also includable by Chasm....

I think this is a more fundamental issue. Chasm map nodes are not designed to be mutated. Besides locals, another example is the root `classes` node. Initially, this was designed...

After some internal debate, the last option seems to be the most popular, so let me elaborate on this. Let's say we have a map like this: ``` locals: {...

I just remembered why this wasn't considered when deciding to structure `classes` as a list: If it was a map, renaming classes would be a bit difficult. While you could...

This is currently pending some investigation into #105 . I think that we can use a list for locals instead, but this needs verification.

This PR is kinda a hack fix to the incositent behaviour of the `NodeUtils.getAs...` methods. Currently, they return null if the value is missing, but throw an exception if it...

I've added a checkstyle file and the gradle plugin. This should probably be mentioned in a CONTRIBUTING.md file. I would still like to add a github workflow to check the...