Frontend proposal page #16
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It looks terrible. I'll redesign it someday.
It has no actual functionality for now. We need to work on integration with the backend. Note: I didn't use the `label` prop in `NativeSelect`, `MultiSelect`, and `Select` because the text looks too small.
Fixed a bug where having an empty or whitespace-only tag in the tag list when submitting a post causes NullReferenceException. Added ElementRequiredAttribute for applying RequiredAttribute to every element in an IEnumerable. In ElementMaxLengthAttribute, changed the element type of the foreach from object to object? to better convey the intent, even though it doesn't change anything.
Also removed some Include calls because ProjectTo didn't need those, except for those in GetPostsByParameters. See the comment for details.
Added related migration files. Modified init.sh to grant the Migrator user DROP privilege so that it can undo migrations.
That is, "proposals" is no longer a dedicated page. Also, I've done some small tweaks on the collapse logic of `Aside`.
- download model in Dockerfile
and whether the currently logged-in user liked or disliked a post.
Removed the mention of "possible values" in the documentation of CurrentUserVoteQueryResponseDto.VoteKind because the Swagger UI already shows the possible values and because it doesn't get displayed in the Swagger UI anyway.
This is to prepare for the integration with the new image and text moderation features on the AI branch.
Added two endpoints that check if a piece of text or image contains inappropriate content using AI. Modified AI/.gitignore to make it ignore .env because it contained an API key. Fixed an issue where in AiController, none of the parameters showed up as required in the Swagger UI (but they were still validated in the backend so not a big issue). Added the generated client code to frontend/openapi.
It can now search for posts with keywords in the title or content. It can use the sorting options, tags, and author filters on the side. Currently, it seems there are no other authors or different publishing times, so I'm not sure if the author filter and publishing time sorting will work properly.
I've finished setting up the AI search, but it might be a bit inconvenient to use. Additionally, the filter options for tags and authors on the side are ready too. You can type a single character, and all tags or authors containing that character will appear.
It will show all proposals by default
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I basically got all the functions done