Skip to content

User profiles#29

Draft
tomast1337 wants to merge 11 commits intodevelopfrom
feature/user-profile
Draft

User profiles#29
tomast1337 wants to merge 11 commits intodevelopfrom
feature/user-profile

Conversation

@tomast1337
Copy link
Copy Markdown
Member

@tomast1337 tomast1337 commented Jan 12, 2025

This PR adds comprehensive features to enhance user profile management and songs and user search functionality

Planned Features:

  • Song search functionality based on keywords

  • User profile search functionality based on keywords

  • User profile pages for viewing member information

  • Profile editing interface for users to manage their details

Nice examples of profiles

Useful links about text search in MongoDB:

@tomast1337 tomast1337 self-assigned this Jan 12, 2025
@tomast1337
Copy link
Copy Markdown
Member Author

tomast1337 commented Jan 15, 2025

@Bentroen
For the user search feature, I created this search box, I assume the same search box can be repurposed for a song search feature, Does this approach seem suitable?

search

@tomast1337 tomast1337 added the help wanted Extra attention is needed label Jan 21, 2025
@tomast1337
Copy link
Copy Markdown
Member Author

@Bentroen To implement a search feature for users and songs is harder than I imagined.

I have a few worries about How efficient searching by keyword, name, title, author, and description by section or substring can be. And, how could we avoid full reads in case some user requests?

@tomast1337 tomast1337 changed the title Feat (profiles): Implement user-profiles and search functionality [WIP] Feat (profiles): Implement user-profiles and user and song search [WIP] Jan 21, 2025
@tomast1337
Copy link
Copy Markdown
Member Author

https://www.mongodb.com/resources/basics/full-text-search

I guess this is the approach to be taken with MongoDB, it already take care of all of this like fuzzy search and indexing is bazeds on words and not full strings.

@Bentroen Bentroen changed the title Feat (profiles): Implement user-profiles and user and song search [WIP] User profiles; user and song search [WIP] Feb 19, 2025
@Bentroen Bentroen marked this pull request as draft February 20, 2025 22:52
@Bentroen
Copy link
Copy Markdown
Member

Bentroen commented Mar 3, 2025

Thanks for working on these features!

@Bentroen For the user search feature, I created this search box, I assume the same search box can be repurposed for a song search feature, Does this approach seem suitable?

Yes, we can have a single search feature that can return results for both users and channels - selectable with a tab widget, similar to what YouTube does.
For simplicity, and since song search would be more useful than searching for users at first, we could implement search only for songs, and leave user search for a later stage.
(It seems like searching for channel is not very common compared to video search, so even YT relegated this option to a separate popup):

I have a few worries about How efficient searching by keyword, name, title, author, and description by section or substring can be. And, how could we avoid full reads in case some user requests?

Since user profiles are such a simple feature compared to search, I believe this PR can be reduced in scope to just user profiles, since they don't rely on search being ready to be merged into production. We can leverage the existing search infrastructure implemented here in a subsequent PR.

@Bentroen Bentroen changed the title User profiles; user and song search [WIP] User profiles Mar 3, 2025
…ator

- Add env, Discord strategy, and song form schemas to @nbw/validation
- Wire ConfigModule to validateEnv; parse user/song/query payloads with Zod
- Replace DTO class helpers with mappers in song.util; re-export validation from @nbw/database for consumers
- Frontend: import song form schemas from @nbw/validation; remove local SongForm.zod
- Remove class-validator/class-transformer and global ValidationPipe from backend
- Update specs; note bun test may need workspace resolution fixes for @nbw/config
- Introduce a new jsonStringField function to validate and parse JSON strings, ensuring invalid JSON surfaces as a Zod issue.
- Update thumbnailData and customInstruments fields to utilize jsonStringField for improved validation.
…instructions

- Change package name to @nbw/validation and clarify its role as the source of shared Zod schemas and TypeScript types.
- Add detailed layout and script sections for building, developing, testing, linting, and cleaning the package.
- Include instructions for consumers on how to import and use the package after building.
- Delete jest.config.js as part of the cleanup process for the validation package.
…TO names

Remove common/types.ts and song/types.ts (PageQueryDTOType and *DtoType aliases).
Add song/uploadMeta.ts for VisibilityType, CategoryType, LicenseType, TimespanType.
Export SongsFolder from SongPage.dto.ts next to SongPageDto.

Point SongPreview/SongView/UploadSongDto at uploadMeta; update package index exports.
Rename frontend imports from *DtoType to the real DTO types (via @nbw/database).
…ckage dependencies

- Introduced new UI components: Button, Input, Label, and Textarea for consistent styling and functionality across the application.
- Added @radix-ui/react-label dependency to package.json for label component integration.
- Updated existing components to utilize the new UI components for improved user experience.
- Refactored ProfileBioEditor and ProfilePublicNameEditor to use the new Input and Button components.
@tomast1337 tomast1337 force-pushed the feature/user-profile branch from 9b0e525 to fb03997 Compare April 18, 2026 00:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

help wanted Extra attention is needed

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

2 participants