Adam Gent
Adam Gent
Apparently my other project had a flag to disable the warning but for a different reason. Would adding an annotation processor flag be amenable for now? Annotation processors look like...
> Using -Xlint:-processing works fine for me for now Yes that is the flag I have set in the other project. I will eventually add a flag as I can...
> It happens at compile time right, so it's easy to spot? That is correct.
I have some hesitations that I can't really formulate yet into words about defaulting to converting kebab-case to camelCase. Partly because kebab-case just happens to not be a valid Java...
Another solution is to use sealed interfaces. We can reuse `JStachePartial`. ```java @JStacheDynamicPartial public sealed interface Shape permits Square, Triangle { } @JStachePartial(template = "...") public record Square(int height, int...
Sealed classes are basically sum types (well with OOP mixed but ignore that). For some reason I thought you had some Haskell experience but I must have mixed that up...
@jgonggrijp sorry for the late follow up but your example would be completely fine because the context stack will be preserved. In the case of some object actually using literals...
A more general pluggable falsey would be better. Closing for now.
Regardless if we do make a more general pluggable falsey we need this feature distinctly separated out for ease of onboarding JMustache users. In JMustache the property is called: `emptyStringIsFalse`....
It is fixed with not an ideal hack so I will leave this open for now.