-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FINERACT-2021: refactor the note GET end-points to use Jackson instead of GSON. #3915
base: develop
Are you sure you want to change the base?
FINERACT-2021: refactor the note GET end-points to use Jackson instead of GSON. #3915
Conversation
@Zeyad2003 let's organize a call... I have some more information for you. Let's leave this PR for the moment as it is, please do not merge. |
1864b4e
to
4e823ce
Compare
4e823ce
to
500702c
Compare
6c1a49b
to
d8bcf0f
Compare
custom/gsoc/note/api/src/main/java/org/apache/fineract/gsoc/note/api/NoteApiController.java
Outdated
Show resolved
Hide resolved
custom/gsoc/note/api/src/main/java/org/apache/fineract/gsoc/note/api/NoteApiController.java
Outdated
Show resolved
Hide resolved
a18e9a2
to
8ce9d8f
Compare
.../src/main/java/org/apache/fineract/typesafe/common/configuration/CommonWebConfiguration.java
Outdated
Show resolved
Hide resolved
8ce9d8f
to
937fd43
Compare
df4bc00
to
2d4f312
Compare
d0e1c4e
to
b6fd5fa
Compare
8e8fef3
to
0c04a7e
Compare
2adb163
to
b715704
Compare
2903b5b
to
8e2db2a
Compare
8e2db2a
to
c637627
Compare
c637627
to
e213868
Compare
…erialization with GSON. - Implemented a new custom module for the note API. - Used Spring Web-MVC annotations instead of JAX-RS. - Dispensed the redundant query parameters like "fields, prettyPrint ..etc" - Implemented a new `CommonWebConfiguration` for establishing the security configurations (not complete yet). - Implemented configuration modules (core, starter, configuration) for configuring the note module. - Implemented a new `docker-compose-api-v3.yml` configuration file.
e213868
to
b0a4077
Compare
What should be done with this PR? |
This pull request seems to be stale. Are you still planning to work on it? We will automatically close it in 30 days. |
Description
Ignore if these details are present on the associated Apache Fineract JIRA ticket.
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.