Feature/JA-122 AdSearchForm component
#117
Merged
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
Change some logic in Browse/Search action to accept serialized search criteria.
skrawus
approved these changes
Jul 3, 2024
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 replaced old search form partial view with a Blazor component. Now search fields are disabled until corresponding checkbox is enabled.
Because
AdSearchCriteriaViewModelneeded to cross MVC-WASM boundary, I moved it to.Blazorproject and I pass it to the component serialized as JSON.When it comes to consuming the form, I realized I don't need to read any of the visible inputs of the form when search criteria are submitted - I just put a hidden input with view model serialized as JSON and each time anything is changed in the form, this JSON is updated. In
Browse/SearchI deserialize it and pass it forward as previously.