Skip to content

Handling failures with selectFarthestJoined using Objects instead of Strings #159

Answered by renggli
GP4cK asked this question in Q&A
Discussion options

You must be logged in to vote

Since error messages are String values, there is (at least for now) no elegant way than to keep track of the combined error messages. Instead of using selectFarthestJoined you could of course copy that small snippet of code and create whatever combined error message you prefer?

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by GP4cK
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants