Skip to content

Conversation

@sidhantgoel
Copy link

@sidhantgoel sidhantgoel commented Aug 11, 2025

Description

  1. The TaxGroup API wasn’t returning any data because the necessary getter annotations were missing, so the fields weren’t being serialized in the response.
  2. There was a spelling mismatch, which caused the TaxComponent APIs to fail.

Both issues have been fixed.

Checklist

Please make sure these boxes are checked before submitting your pull request - thanks!

  • Write the commit message as per https://github.com/apache/fineract/#pull-requests
  • Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
  • Create/update unit or integration tests for verifying the changes made.
  • Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.
  • Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes
  • Submission is not a "code dump". (Large changes can be made "in repository" via a branch. Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

@adamsaghy
Copy link
Contributor

@sidhantgoel Please rebase with latest develop branch.

private BigDecimal percentage;
private Integer debitAccountType;
private Long debitAccountId;
private Long debitAcountId;
Copy link
Contributor

Choose a reason for hiding this comment

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

typo...

Copy link
Author

@sidhantgoel sidhantgoel Aug 14, 2025

Choose a reason for hiding this comment

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

it is not a typo, intentional because this is the spelling used in many places including web app.

Copy link
Contributor

Choose a reason for hiding this comment

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

I think this must be set to debitAccountId, if it exists in other parts of the Apache Fineract then it must be fixed. WebApp is not an Apache Fineract Project.

Copy link
Contributor

Choose a reason for hiding this comment

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

@sidhantgoel As Victor stated, please dont introduce typos into the Fineract backend! Kindly asking you to fix the UI instead.

Copy link
Contributor

Choose a reason for hiding this comment

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

@sidhantgoel Please undo this!

String sql = "select " + TAX_COMPONENT_MAPPER.getSchema();
return this.jdbcTemplate.query(sql, TAX_COMPONENT_MAPPER); // NOSONAR
return this.jdbcTemplate.query(con -> con.prepareStatement(sql,
ResultSet.TYPE_SCROLL_SENSITIVE,
Copy link
Contributor

Choose a reason for hiding this comment

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

why do we need this: ResultSet.TYPE_SCROLL_SENSITIVE, ?

Copy link
Author

Choose a reason for hiding this comment

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

If we dont use this, the resulset returned in case of PostgreSQL we can navigate in only one direction. but since we are moving back in some cases a scrollable result set is required.

Copy link
Contributor

@adamsaghy adamsaghy left a comment

Choose a reason for hiding this comment

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

Please review my comments!
Testing is missing, please make sure to attach proper test cases which ensures the fixed, correct behaviour!

@adamsaghy
Copy link
Contributor

@sidhantgoel Please squash your commits!

@sidhantgoel
Copy link
Author

@adamsaghy done

@sidhantgoel
Copy link
Author

@adamsaghy would you be able to review it please.

@adamsaghy
Copy link
Contributor

@adamsaghy would you be able to review it please.

@sidhantgoel Please fix the failing tests first!

@sidhantgoel
Copy link
Author

@adamsaghy Is there a document on how to run test cases locally?

@adamsaghy
Copy link
Contributor

@adamsaghy Is there a document on how to run test cases locally?

you can find some materials on my website: www.fineract-academy.com

@sidhantgoel
Copy link
Author

@adamsaghy fixed the errors.

@adamsaghy
Copy link
Contributor

Please use appropriate FINERACT jira number in the title and in the commit message!
See example: #4932

@sidhantgoel
Copy link
Author

There is no jira ticket for this, shall I create one?

@sidhantgoel sidhantgoel changed the title Minor fixes to make it work with PostgreSQL and response fix for TaxGroup FINERACT-2351: Minor fixes to make it work with PostgreSQL and response fix for TaxGroup Aug 23, 2025
…fix variable name typos in TaxComponentRequest; update SQL query preparation in TaxReadPlatformServiceImpl for PostgreSQL compatibility.
@sidhantgoel
Copy link
Author

@adamsaghy is it ok now?

public List<TaxComponentData> retrieveAllTaxComponents() {
String sql = "select " + TAX_COMPONENT_MAPPER.getSchema();
return this.jdbcTemplate.query(sql, TAX_COMPONENT_MAPPER); // NOSONAR
return this.jdbcTemplate.query(con -> con.prepareStatement(sql, ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE),
Copy link
Contributor

Choose a reason for hiding this comment

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

I am not convinced we need ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE), this services just retrieve a List of TaxComponentData AS-IS, no any iteration on them back or forth...

Can you help me to understand why this is an issue?

Copy link
Contributor

@adamsaghy adamsaghy left a comment

Choose a reason for hiding this comment

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

Kindly see my review and concerns!
Also please make sure the functionality to be covered with test cases to ensure, now it works as expected!

@github-actions
Copy link

This pull request seems to be stale. Are you still planning to work on it? We will automatically close it in 30 days.

@github-actions github-actions bot added the stale label Sep 28, 2025
@IOhacker
Copy link
Contributor

@sidhantgoel are you still working on it?

@github-actions github-actions bot removed the stale label Oct 15, 2025
@github-actions
Copy link

This pull request seems to be stale. Are you still planning to work on it? We will automatically close it in 30 days.

@github-actions github-actions bot added the stale label Nov 14, 2025
@adamsaghy
Copy link
Contributor

@sidhantgoel Are you still working on this?

@github-actions github-actions bot removed the stale label Nov 26, 2025
@adamsaghy adamsaghy marked this pull request as draft December 2, 2025 09:07
@github-actions
Copy link

github-actions bot commented Jan 2, 2026

This pull request seems to be stale. Are you still planning to work on it? We will automatically close it in 30 days.

@github-actions github-actions bot added the stale label Jan 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants