Equivalent to NoResult Exception when updating from older versions

Open
#1,182 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
php
Domain
backend

Research direction

No source file, test, or entry point is identified in the issue. Compare the older and current exception APIs around Geocoder\Exception\NoResult, then check the project’s migration or exception documentation. Done means documenting the supported replacement or clearly stating whether the generic exception should be used.

Written by the indexing model from the issue text.

Description

question

Hi, im updating my project and i came across this problem. I have some uses for Geocoder\Exception\NoResult, but those no longer exist.
Are there any equivalents? Or should i use the generic exception for this cases?

Dominant language
PHP
Stars
4k
Forks
525
Avg merge
8m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from geocoder-php/Geocoder

All issues in geocoder-php/Geocoder

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.