Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Default visitor context generates invalid URNs

Open
#87 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java

Research direction

Start by tracing how VisitorContext uses ResolvedType.toCanonical() to create the default URN, then inspect Jackson core implementations such as SimpleType that emit '<' and '>' for type parameters. Check the RFC 2141 character restrictions and verify that default URNs no longer contain those characters while preserving the override behavior.

Written by the indexing model from the issue text.

Description

VisitorContext uses ResolvedType.toCanonical() to create the URN. Problem is implementations of toCanonical in Jackson core types use '<' and '>' to denote type params(e.g. SimpleType). These two characters are excluded from the RFC for URNs: https://www.ietf.org/rfc/rfc2141.txt. Even though you can override the URN generation, I think the default behavior should not generate invalid URNs.

Dominant language
Java
Stars
387
Forks
138
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 FasterXML/jackson-module-jsonSchema

All issues in FasterXML/jackson-module-jsonSchema

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.