and RoleMapper

This commit removes an unnecessary blank line in the PersonMapper class. The removal cleans up the code and improves its readability. This change adheres to the defined code style guide.

…-native-api

# Conflicts:
#	src/main/java/com/sublinks/sublinksapi/api/lemmy/v3/site/controllers/SiteController.java

The code refactor involved updating PersonService's relevant methods and adjusting their arguments and properties. Alongside this, JSON Web Token (JWT) authentication has been implemented to secure APIs. A new process for person registration has also been introduced, which now includes email verification and handling different registration modes. New components such as JwtFilter, JwtUtil and JwtPerson have been included for managing JWTs, and a new timeline endpoint for default controller is also introduced.

…PI functionality

Made changes throughout the project by replacing primitive boolean with its Wrapper class, Boolean. This allows for null values, which can represent 'undefined' status. In addition, introduced new community-related endpoints and services, for enhanced community details management. Also, new SortType and ListingType enumerations were added, to enrich the sorting and listing options. Implemented relevant conversions and mapping for new types.

Added method to find Instance by domain in the InstanceRepository and find methods for Community in the CommunityRepository. Enhanced SublinksCommunityService to handle community updates, deletion and removal, and validate unique titleSlugs upon creation. Also introduced ActorIdUtils for handling actorIDs.

Added SublinksCommentService for handling comment creation with proper validations and exception handling. Adjusted RoleAuthorizingService by introducing helper methods to check a person's permission status. Updated CommunityModActionsController with refined exception handling logic. Added necessary find methods in PostRepository and CommentRepository. Introduced new model classes for comments.

CommunityRepository has been refactored to use Optional for the return type of findCommunityByTitleSlug method to better handle absence of value situations. Additionally, logic has been added in createCommunity and updateCommunity methods to check user permissions for these operations. The updateCommunity method has also been simplified for better readability and efficiency.

This commit renames classes related to JWT authentication for coherence and better readability. It also includes a new column in the Language entity to handle language codes. Furthermore, a validation has been added to check language availability while creating comments. Minor syntax changes are also performed to improve readability and comply with updated editor settings. This refactoring ensures better code organization and enhances functionality by accepting comments in different languages.

# Conflicts:
#	src/main/java/com/sublinks/sublinksapi/api/lemmy/v3/community/controllers/CommunityModActionsController.java
#	src/main/java/com/sublinks/sublinksapi/api/lemmy/v3/community/controllers/CommunityOwnerController.java
#	src/main/java/com/sublinks/sublinksapi/api/lemmy/v3/post/controllers/PostController.java
#	src/main/java/com/sublinks/sublinksapi/api/lemmy/v3/user/controllers/UserAuthController.java
#	src/main/java/com/sublinks/sublinksapi/authorization/services/RoleAuthorizingService.java
#	src/main/java/com/sublinks/sublinksapi/person/repositories/PersonRepository.java
#	src/main/java/com/sublinks/sublinksapi/person/services/PersonService.java
#	src/main/java/com/sublinks/sublinksapi/person/services/UserDataService.java

Removed irrelevant code block in PersonService and improved formatting across various methods in CommunityModActionsController and PostController to improve readability and maintain consistency. Arranged method calls and parameters to make the code cleaner and easier to understand.

The authentication config has been refactored and the APIs related to JWT filter, person, and community have been updated. The changes include filename changes, code reformatting, function renaming, and improved access control checks.

This commit refactors several controller classes for better code organization and consistency. Classes were renamed, and the RestController annotation was added to each controller. Additionally, the implementation of JWT filter was updated to improve authentication security. Improvements to the build file were also made, adding additional dependencies.

…ences

The enum 'ListingType' was renamed to 'SublinksListingType' to be more specific. All references in the code to the old 'ListingType' has been updated to 'SublinksListingType'. Additionally, the boolean 'showNsfw' in IndexCommunity class was updated to not use Optional.

New models, CommunityView and CommunityAggregates, were introduced to provide comprehensive information about communities. The SublinksCommunityController was also updated to use these models, thereby improving the details provided when fetching a community or list of communities.

This reverts commit a76268e

This reverts commit 05a030b.

This reverts commit 0d47e47.

…/119-native-api

This reverts commit 171f0b7.

This reverts commit a76268e.

This reverts commit 05a030b.

This reverts commit 0d47e47.

Designed and implemented moderation functionalities in the Sublinks community. This includes obtaining community moderators, adding and deleting moderators, and the capacity to ban users. Fixed the API paths for some services and introduced new types and mapper classes to align with the new moderation features.

The commit introduces methods to ban and unban users from a community. To implement this change, a new import for PersonRepository was added to the SublinksCommunityService class. New endpoints for "ban" and "unban" were added to the SublinksCommunityModerationController. The findOneByName method in PersonRepository was replaced with findOneByNameIgnoreCase to ensure the case insensitivity of username in ban/unban requests. In addition, The LinkPersonCommunityService class was updated to handle the removal of any user link in case of banning.

In this update, several features were added to the community services including the ability to create, update, and retrieve communities. In addition, functionality to manage moderation including getting community moderators and banning/unbanning persons was introduced. Also introduced initial pieces for posting functionality with new models and mapping methods. Necessary documentation for these features was added in addition to minor formatting changes.

This commit breaks down the original combined setters and condition checks in UserController when updating the Person object. This makes the code more readable and ensures that each field is properly checked before assignment. The code is now more maintainable, as each operation is clearly isolated.

The change have been made in the SublinksCommentController class, specifically in the index method, to return a list of CommentResponse objects instead of a single object. This is a more efficient way to handle multiple comments.

The commit adds the ability to view, create and edit comments. Updates were made to the community service to provide functionality for retrieving a list of communities based on certain criteria, creating a comment, and updating comments. The addition of authorization checks was also made in several places to ensure only authorized users can perform certain operations. Additionally, functionalities were created to interact with community moderators and community aggregation.

This commit significantly enhances the ban logic and introduces the community remove feature in the community moderation functionality. Specifically, the ban logic has been updated to allow both banning and unbanning of users. The commit adds a remove method that enables moderators to remove communities based on roles and permissions for both admin and moderator roles have been updated accordingly. As part of this enhancement, several record models related to community moderation have been updated or created.

This commit significantly enhances the ban logic and introduces the community remove feature in the community moderation functionality. Specifically, the ban logic has been updated to allow both banning and unbanning of users. The commit adds a remove method that enables moderators to remove communities based on roles and permissions for both admin and moderator roles have been updated accordingly. As part of this enhancement, several record models related to community moderation have been updated or created.

…/119-native-api

Signed-off-by: Pdzly <[email protected]>

Introduced delete and remove functionality to both community and comment sections of the platform. Changed tag names in community controllers for better clarity. Updated Community and Comment services to support new moderation features. Also, made minor adjustments to PostMapper and RolePermissionCommentTypes for better code organization.

The commit includes the implementation of a new comment pinning feature in the comment service and controller, which will allow moderators to pin and unpin comments. It also includes changes in HTTP methods from 'GET' to 'POST' in several places to align with REST best practices for methods that change the state of the data. Some formatting adjustments for improve code readability are also included.

Signed-off-by: rooki <[email protected]>

This commit introduces the ability for moderators to pin and unpin comments through the new functionality in the comment service and controller. It also replaces several 'GET' HTTP methods with 'POST' for compliance with REST standards on state-changing operations. Additionally, some code formatting was adjusted for better readability.

Signed-off-by: rooki <[email protected]>

This commit updates and enhances the application in multiple ways. It includes refactoring classes that have been moved to more appropriate packages and renaming some of them for better understanding. Furthermore, new functionalities have been introduced such as implementing a service to ban a user and a service to retrieve a list of banned users. The code also contains improved error handling and minor modifications for improving code quality.

Signed-off-by: rooki <[email protected]>

Signed-off-by: Rooki <[email protected]>

Changes have been made to refactor the `SublinksPersonAggregationController`. The controller now makes use of the `PersonAggregateResponse` and `PersonIdentity` models. In addition, authentication checks have been added to ensure a user has the correct permissions before accessing certain data.

Signed-off-by: rooki <[email protected]>

The commit introduced more detailed authorization checks in various parts of the application. It further enriched the response models for better client-side readability. Moreover, annotation responses have been updated in multiple controllers to improve the OpenAPI documentation.

Signed-off-by: rooki <[email protected]>

Introduced search functionality in the Instance Repository to retrieve instances based on domain or description. Enhanced various controllers for better data handling and error management. Updated the InstanceConfig and Person Repositories for increased efficiency. Enhanced the application's mapping capabilities by introducing a new SublinksInstanceMapper. Added RegistrationMode and ListingType enums for better data management in instances.

Signed-off-by: rooki <[email protected]>

Signed-off-by: rooki <[email protected]>

In this update, the Search API has been expanded to include not only person-related responses but also community, post, and comment responses. A new service, SublinksSearchService, has been added, along with several model updates to support these features. Additionally, code adjustments have been made to adapt the parameter renaming of 'limit' to 'perPage'.

Signed-off-by: rooki <[email protected]>

Code has been refactored for better readability and new methods have been added to the Builder class in PostSearchQueryService.java for filtering NSFW posts and to perform a search. Improvements to code structuring have been made across multiple files to enhance readability. Additionally, search functionality parameters have been added to the IndexCommunity.java file.

Signed-off-by: rooki <[email protected]>

Refactored code for increased readability, and added new methods for NSFW post filtering and search functionality in PostSearchQueryService.java. Enhanced overall code structuring across various files, and incorporated search function parameters within IndexCommunity.java.

Signed-off-by: rooki <[email protected]>

This commit refactors the PostReportRepositoryImpl and PostLikeRepositoryImpl classes, aiming to improve the code readability and maintainability. Changes include updating the method argument structure, introducing the use of the applyPagination utility function to manage pagination in queries, and reformatting the code for increased readability.

Signed-off-by: rooki <[email protected]>

Several new methods and imports have been added to the SublinksPostService. The `show` method allows to find and display a specific post based on a key and a person, performing various checks to ensure post visibility. The `create` method executes complex functionality to create a new post. Furthermore, CreatePost model has also been updated with new parameters to support these changes.

Signed-off-by: rooki <[email protected]>

# Conflicts:
#	src/main/java/com/sublinks/sublinksapi/api/lemmy/v3/post/controllers/PostController.java
#	src/main/java/com/sublinks/sublinksapi/api/lemmy/v3/user/controllers/UserController.java
#	src/main/java/com/sublinks/sublinksapi/authorization/services/InitialRoleSetupService.java
#	src/main/java/com/sublinks/sublinksapi/comment/repositories/CommentRepository.java
#	src/main/java/com/sublinks/sublinksapi/post/repositories/PostRepositoryImpl.java
#	src/main/java/com/sublinks/sublinksapi/post/services/PostSearchQueryService.java

This commit includes enhancements to the 'Post' object. Language restrictions are added, checks whether the post language is supported by the community or instance are implemented. A Slur filter has been integrated to handle exception scenarios and it can censor text in post bodies. Additionally, metadata from the linked website, if a link is provided in the post, is fetched and stored.

Signed-off-by: rooki <[email protected]>

This update introduces the comment aggregate API, providing insights on aggregate data like upvotes, downvotes, hot rank and reply count per comment. Furthermore, it broadens the post functionalities by introducing language restrictions and enforcing to check if the chosen language is supported by the respective community or instance. The slur filter integration helps in text censorship within post bodies, and links within posts now have metadata fetching and storing ability.

Signed-off-by: rooki <[email protected]>

This update introduces the comment aggregate API, providing insights on aggregate data like upvotes, downvotes, hot rank and reply count per comment. Furthermore, it broadens the post functionalities by introducing language restrictions and enforcing to check if the chosen language is supported by the respective community or instance. The slur filter integration helps in text censorship within post bodies, and links within posts now have metadata fetching and storing ability.

Signed-off-by: rooki <[email protected]>

The diff shows a particular comment section being removed from a SQL migration script. The comment is no longer relevant or necessary, thereby enhancing the clarity and readability of the code.

Signed-off-by: rooki <[email protected]>

# Conflicts:
#	src/main/java/com/sublinks/sublinksapi/comment/models/CommentSearchCriteria.java

This update added announcement handling functionality to Sublinks API. It includes creation of new model classes, updating service layers with query methods, and CRUD operations in the controller. It also added local people filtering to the `SublinksPersonService`.

Signed-off-by: rooki <[email protected]>

The commit introduces full CRUD functionality for announcements in the Sublinks API. It includes creation of new Announcement models with related update and removal forms. Implementation includes service updates, repository additions, and corresponding changes in the Announcement Controller.

Signed-off-by: rooki <[email protected]>

Added an 'active' status field to announcements, allowing for them to be toggled on and off. The 'creator' field was also added to link announcements to the user who created them. Renamed a comment mapper class, added a few new mapper classes and adjusted controller methods to accommodate these changes. Meanwhile, made adjustments to database queries and schemas to align with these updates.

Signed-off-by: rooki <[email protected]>

Moved permissions checks from controller to service layer to ensure better encapsulation. This change affects SublinksCommunityController, SublinksCommentAggregateController, and SublinksCommentModerationController. An ADMIN_UPDATE_COMMUNITY permission was also added in RolePermissionCommunityTypes. This improves code maintainability and readability.

Signed-off-by: rooki <[email protected]>

Introduced new endpoints in the SublinksPersonSessionController to allow managing user metadata including getting, invalidating, and deleting metadata. Specific permissions have been added to govern these actions. Two new models, PersonSessionData and PersonSessionDataResponse, have been included to manage data transfer. Enhancements are made in services for consistent permission checks and handling new operations.

Signed-off-by: rooki <[email protected]>

# Conflicts:
#	src/main/java/com/sublinks/sublinksapi/api/lemmy/v3/authentication/config/SecurityConfig.java

This commit simplifies the code in the SecurityConfig.java file for the security configuration of the Lemmy V3 API. It removes some duplication in the code related to session management and the authorization of HTTP requests, and changes the order of the `addFilterBefore` method to execute after session management.

Signed-off-by: rooki <[email protected]>

The JWT filter addition is rearranged in the SecurityConfig. Previously, it was added before configuring CSRF, securityMatcher, authorization, and sessionManagement. Now, it is added after configuring all these. This change ensures that the JWT filter gets executed at the correct point in the filter chain.

Signed-off-by: rooki <[email protected]>

The commit removes unused methods and imports from the SublinksPersonMetaDataMapper class. The 'updatedAt' mapping source has also been changed from 'metadata.updatedAt' to 'metadata.lastUsedAt'. Besides, the 'mapPersonKey' method and associated Person import have been removed since they are no longer being used.

Signed-off-by: rooki <[email protected]>

Significant improvements have been added to the management of user data and user sessions. The changes include the correction of certain URL Utilities, updates to the pagination functionalities, and enhancements to the handling of user metadata and validation mechanisms. Additionally, there are changes to the roles functionality, focusing on improving permissions handling, and also improvements on the structure of the API responses, and creation of essential utilities for person key handling.

Signed-off-by: rooki <[email protected]>

The UserDataService has been refactored for simpler active user data retrieval and updating. The fetching process has been simplified by removing the need to fetch data using person and IP address together. Also, the metadata update procedure has been improved; it no longer needs to instantiate a new metadata every time there's a change, but instead, modifies the existing metadata instance.

Signed-off-by: rooki <[email protected]>

The import statements in the UserDataService class have been reordered. This change improves readability and adheres to code style guidelines. No functional changes have been made to the code.

Signed-off-by: rooki <[email protected]>

The methods for showing and updating instance configurations now require the user's identity. The server will throw unauthorized responses when requested by unauthorized people. Permission types for reading and updating instances were added to the RolePermissionInstanceTypes enumeration.

Signed-off-by: rooki <[email protected]>

Renamed moderation models for consistency and clarity, and updated all relevant methods in service and controller classes accordingly. Two new models for Post moderation were added. Additionally, fixed logic in checking delete post permission in SublinksPostService.

Signed-off-by: rooki <[email protected]>

Renamed Aggregate model classes to unify nam

Signed-off-by: rooki <[email protected]>

The code alters several parts where a moderator could remove certain entities. The action has now been changed to pinning the entities instead. This includes changes in comments, posts, and community moderation. Additional adjustments have been made to ensure correct behaviour of the new pin functionality.

Signed-off-by: rooki <[email protected]>

A new operation to purge a community was added to the Sublinks Community Moderation Controller. This operation, however, is still not implemented and will be completed in the future. The summary text for the delete operation in the Sublinks Community Controller was changed from 'Purge an community' to 'Delete a community'.

Signed-off-by: rooki <[email protected]>

New functionalities added to SublinksPostModerationController: pinning a post, pinning a post in a community, and purging a post. The implementation for purging a post is not complete yet, but will be in future iterations. Additionally, the description for the Post Moderation API is updated. Existing functionality in the SublinksPostService is adjusted to allow the "featured" status of a post to be toggled during the pinning process.

Signed-off-by: rooki <[email protected]>

Enhancements were made to various API functionalities, including the addition of Instance Search and revised Private Message features. An array of new dependencies and properties were defined for instances and private message search criteria. SearchScopes now encompass posts, comments, communities, and instances. The changes aim to improve the user's search experience across categories and streamline the process of private message handling.

Signed-off-by: rooki <[email protected]>

The "purge" functionality has been removed from the SublinksCommunityModerationController. Additionally, unneeded component and dependencies were removed from the SublinksCommunityController, and the constructor in SublinksPrivatemessageModeratorController was replaced with @AllArgsConstructor for brevity.

Signed-off-by: rooki <[email protected]>

The request mapping for the SublinksPostAggregateController class has been updated. Previously, it was incorrectly mapped to "api/v1/comment/{key}/aggregate". It has been corrected to "api/v1/post/{key}/aggregate".

Signed-off-by: rooki <[email protected]>