Skip to content

Fix typo: MissingInjectableValueExcepion → MissingInjectableValueException - #5621

Merged
cowtowncoder merged 3 commits into
FasterXML:3.xfrom
dlwldnjs1009:fix/typo-MissingInjectableValueException
Jan 28, 2026
Merged

Fix typo: MissingInjectableValueExcepion → MissingInjectableValueException#5621
cowtowncoder merged 3 commits into
FasterXML:3.xfrom
dlwldnjs1009:fix/typo-MissingInjectableValueException

Conversation

@dlwldnjs1009

@dlwldnjs1009 dlwldnjs1009 commented Jan 28, 2026

Copy link
Copy Markdown
Contributor

Summary

Fix typo in exception class name:
MissingInjectableValueExcepionMissingInjectableValueException (missing "t").

  • Added correctly named exception as sub-type of existing one
  • Deprecated existing exception
  • Updated all in-repo references (prod + tests)

Test plan

  • ./mvnw test -pl . -Dtest="JacksonInject*Test"

…ption

Rename class introduced in FasterXML#5156 that was missing "t" in "Exception".
Updated all references in DeserializationContext and test files.
@github-actions

Copy link
Copy Markdown

🧪 Code Coverage Report

Metric Coverage Change
Instructions coverage 80.21% 📈 +0.000%
Branches branches 73.27% 📈 +0.000%

Coverage data generated from JaCoCo test results

@cowtowncoder

Copy link
Copy Markdown
Member

Yes, we must retain old name as deprecated -- new correctly named one should be... sub-class, I think, of the now-deprecated wrongly-named class. That way if any existing code is catching or checking type with old class, things will still work.

@cowtowncoder cowtowncoder left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As per my note, we must retain old incorrectly named exception type, deprecate it, and add new correctly named sub-type. This for 3.0-compatibility.

…bility

Re-introduce the old misspelled class as a @deprecated base class
(extends DatabindException) with fields and accessors intact.
MissingInjectableValueException now extends the deprecated class as
a thin subclass, preserving type compatibility for existing code that
catches or checks the old exception type.

- MissingInjectableValueExcepion: deprecated base with fields, getters,
  and from() factory that delegates to the new subclass
- MissingInjectableValueException: thin subclass with constructor and
  from() only (fields/getters inherited)
- Added backward-compatibility test verifying instanceof relationship
@dlwldnjs1009

Copy link
Copy Markdown
Contributor Author

Thanks for the guidance! Updated in d0504b5:

  • Restored MissingInjectableValueExcepion as a @deprecated base type
  • Made MissingInjectableValueException a thin subclass
  • Added a test to verify instanceof-based backward compatibility

This keeps existing catch/check logic working in 3.x.

@github-actions

Copy link
Copy Markdown

🧪 Code Coverage Report

Metric Coverage Change
Instructions coverage 80.21% 📈 +0.000%
Branches branches 73.28% 📈 +0.010%

Coverage data generated from JaCoCo test results

Object valueId, BeanProperty forProperty, Object beanInstance)
{
return new MissingInjectableValueExcepion(p, msg, valueId, forProperty, beanInstance);
return MissingInjectableValueException.from(p, msg, valueId, forProperty, beanInstance);

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 good idea

@cowtowncoder cowtowncoder left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@github-actions

Copy link
Copy Markdown

🧪 Code Coverage Report

Metric Coverage Change
Instructions coverage 80.21% 📈 +0.000%
Branches branches 73.27% 📈 +0.000%

Coverage data generated from JaCoCo test results

@cowtowncoder
cowtowncoder merged commit 48f9e55 into FasterXML:3.x Jan 28, 2026
6 checks passed
@dlwldnjs1009
dlwldnjs1009 deleted the fix/typo-MissingInjectableValueException branch January 28, 2026 03:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants