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

Add support for java records

Open
#1,163 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java
Domain
backend

Research direction

Read the base pom.xml and the recordName template example first, then trace the existing Java-object property resolution behavior. Done means {{ myRecord.recordName }} renders without an explicit getter, with the required Java-version implications addressed and regression coverage added.

Written by the indexing model from the issue text.

Description

public record MyRecord(String recordName) {

	/**
	 * without explicit getter Jinjava doesn't see it
	 */
	public String getRecordName() {
		return recordName;
	}
}

The following template won't be correctly filled without the getter, although it's not needed for records

{{ myRecord.recordName }}

I tried to contribute, but it turned out, that the java version in the base pom.xml is still 8. https://github.com/HubSpot/basepom/blob/master/pom.xml#L17. I think such change must be done by the core maintainers, who know all of the possible implications.

It's 2024, time to go for java 21+

Dominant language
Java
Stars
785
Forks
184
Avg merge
6d 22h
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 HubSpot/jinjava

All issues in HubSpot/jinjava

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.