Skip to content

Conversation

@tWizT3ddreaMr
Copy link
Contributor

This allows a user to view their own history. I didn't want the same thing to be repeated a third time so i made a method .

I couldn't for the life of me come up with a good name for the method, so I left it at the working name for making sure it all worked.

#326 #556

Didnt want the same thing to be repeated a third time so i made a method and named it an absolutely wrong name but cant thing of a a good name so i am leaving it with a bad until feedback
Somehow i accidentally merged the imports
I initially wrote this before I updated the branch "Full History", so it made more sense to have an array.
So I rearranged it to better match the layout in PunishmentManager
I missed that error, but saw in the maven check that it failed because of it
I didnt say true when it was history
so it was just throwing all the errors
Copy link
Collaborator

@Hopefuls Hopefuls left a comment

Choose a reason for hiding this comment

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

Please refer to the comments provided in this review.

import java.util.Calendar;
import java.util.GregorianCalendar;
import java.util.List;
import java.util.*;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Please define the imports required that are relevant for the changes rather than using a wildcard.

HISTORY("ab.history",
"\\S+( [1-9][0-9]*)?",
HISTORY(null,
"\\S+( [1-9][0-9]*)?|\\S+|",
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can you clarify this change?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Why I did it this way, I have no idea, as it has been like two years.
But it seems like it is because because I split up the self history's own perm.

I was trying to do what was asked,  however, I couldn't as the line didn't exist, however this redundant import did
@tWizT3ddreaMr
Copy link
Contributor Author

The requested change couldn't happen because it no longer existed likely due to the outdated tag

@Hopefuls
Copy link
Collaborator

Hopefuls commented Apr 1, 2025

Could you revise your changes to the state of development-future? If you wish to continue working on this.

Otherwise I might close this pull request

@tWizT3ddreaMr
Copy link
Contributor Author

Let me check out that branch, and I will respond again within a week. I don't imagine it will be difficult, but I don't have the same development and test environment as when I originally worked on it.

@tWizT3ddreaMr
Copy link
Contributor Author

Yeah my time over the next week or so hasn't cleared up.
If things change I will submit a new pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants