-
Notifications
You must be signed in to change notification settings - Fork 164
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
[#2265][#2267]Fix outdated suggested solution for backend Task 1 #2268
[#2265][#2267]Fix outdated suggested solution for backend Task 1 #2268
Conversation
.registerTypeAdapter(FileType.class, new FileType.FileTypeSerializer()); | ||
.registerTypeAdapter(FileType.class, new FileType.FileTypeSerializer()) | ||
.registerTypeAdapter(ZoneId.class, (JsonSerializer<ZoneId>) (zoneId, typeOfSrc, context) | ||
-> new JsonPrimitive(zoneId.toString())); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The serialization of zoneId has been updated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For this change, I think it will be better to update on your PR. I will keep an eye on which PR is merged first
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yup please change it alongside your PR @CYX22222003 since this is an easy change, lets keep it scoped correctly
|
||
1. Add the following content to `CliArguments` to include `isPrettyPrintingUsed` as a new attribute to the class. | ||
|
||
```java | ||
protected boolean isPrettyPrintingUsed; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there any specific reason that we should change the access modifier to private
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the protected
is already changed into private
due to refactoring.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I apologise for my lack of familiarity with the code, but can you point out for me when the refactoring occurred? I can't seem to find the commit...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you can change this to private since other arguments in CliArguments are using private; this will make it more uniform
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
||
1. Add the following content to `CliArguments` to include `isPrettyPrintingUsed` as a new attribute to the class. | ||
|
||
```java | ||
protected boolean isPrettyPrintingUsed; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you can change this to private since other arguments in CliArguments are using private; this will make it more uniform
.registerTypeAdapter(FileType.class, new FileType.FileTypeSerializer()); | ||
.registerTypeAdapter(FileType.class, new FileType.FileTypeSerializer()) | ||
.registerTypeAdapter(ZoneId.class, (JsonSerializer<ZoneId>) (zoneId, typeOfSrc, context) | ||
-> new JsonPrimitive(zoneId.toString())); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yup please change it alongside your PR @CYX22222003 since this is an easy change, lets keep it scoped correctly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work on your first PR! A few minor nitpicks:
- Since both issues are concerning the same task (updating the outdated docs that contain deprecated classes), it would be cleaner to merge the issues in the future, though that's just my preference.
- It might be more convenient for future members if the commit message body could briefly explain why the docs are being updated.
- The naming of the PR title should follow the convention [#ISSUE_NUMBER] (short brief of PR)
|
||
1. Add the following content to `CliArguments` to include `isPrettyPrintingUsed` as a new attribute to the class. | ||
|
||
```java | ||
protected boolean isPrettyPrintingUsed; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I apologise for my lack of familiarity with the code, but can you point out for me when the refactoring occurred? I can't seem to find the commit...
reiterating with @sopa301 on point 1, you can edit the issue to add on to the tasks to resolve since they are both in the same overarching theme of "outdated DG for learning the basics" rather than creating two separate issues, it can make the issues board "unhygenic" and cluttered over time Since the issues are already created it is fine, we will close both issues once the PR is merged, but do take note in the future. Reiterating on @sopa301 's point 3, we will only merge the PR after the relevant conventions has been complied to so do make the changes! |
The following links are for previewing this pull request:
|
Fixes #2265
Fixes #2267
Proposed commit message