JonMcPherson
Should methods such as IsFull() or IsShort() be converted to properties?
In order to improve consumption of the library by .NET developers, I'd suggest that a few methods should be converted to properties. This is a breaking change and should be undertaken before the OLC library gets a too wide use.
What methods were you thinking could be converted to properties?
I have thought the same thing and have considered changing Decode() to a property that simply returns the CodeArea object which is decoded during construction. I ultimately decided against this because Decode() can only be called on full codes, otherwise an InvalidOperationException is thrown and we don't want to have property getters that can throw an exception on valid OpenLocationCode objects. This implementation is currently following the same design as the Java implementation, but perhaps we could improve the design by separating full and short codes to a different class or interface to avoid all of the various constraints at runtime and to instead design the class model around them.
You are right, but this would require some significant rewrite. I'd rather only refactor the class superficially and change IsFull and IsShort to properties. I'll see if I can find some time to provide a pull request with my proposed changes.