chore: change bool to enum for is_key_within_radius_and_unavailable for better errors #974
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was wrong?
I was debugging gossip and then getting
Which is very unhelpful because then I need to manually check both the content in relation to the radius and if it is already stored.
How was it fixed?
By changing the bool to a enum, this allows us to better define warnings decreasing the guessing games when debugging. Checking if the content is outside of the radius requires quite a bit of setup to calculate if you aren't already prepared for it.
Checking if the content is stored is also work.
So I just made it so the error can be clear and direct in what the problem is. This decreases the work understanding the logs a lot which is a life saver when you are stairing at logs all day.