Change return type of Book#asText in the example about eo

[yegor256]

@Tradunsky I think I agree. text will be a better name. Can you submit a pull request?

[Tradunsky]

@yegor256 Yep, sure. #63

[nqafield]

@Tradunsky Have you got any examples of what you mean by Object#toString being misused?

Also, if Text would be for human-readable text, why wouldn't a book title count as Text? Or even an ISBN for that matter?

[Tradunsky]

@pa9ey, @yegor256
The intention to get rid of String might be a good idea, but first of all we should think of a problem that we are going to solve.

Performing code review for youth engineers I saw some interesting logic based on Type#toString result. According to javadoc:

Returns a string representation of the object. In general, the
{@code toString} method returns a string that
"textually represents" this object. The result should
be a concise but informative representation that is easy for a
person to read.

So, if the method asText supposed to be useful for humans (debugging at least), it should not provide developers with methods for processing it incorrectly.

The second problem is related to representation of basic data as String(or Text). For example, why do we should represent money as string literal? Shall this kind of a type has their own representation, like without quotes (1$, 25uah, 100500rub)? I know that we should choose the level of abstraction in the case of ISBN or Person name, but it looks strange to choose Text for one word or a number. However, the source of that data might be a unknown and it would be easy to create some complex objects from basic type like String.

[yegor256]

@Tradunsky I think this ticket can be closed as fixed?

[Tradunsky]

@yegor256 It is up to you

[yegor256]

@Tradunsky not relevant anymore, thanks for submitting though