Fix: Creation of Events, service providers. #1419
Closed
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
fix: fallback image now provided
Removed unnecessary null assignments for `vendor_id` and `action_id` in `StoryForm.js`. This simplifies the code and avoids potential conflicts.
By setting "IS_CANARY" to false, we ensure production stability.
This was
linked to
issues
Aug 21, 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.
Summary / Highlights
This PR addresses the issue where the forms for creating events and service providers were not working due to the inclusion of extra data fields that the backend was not expecting. These unnecessary fields have been removed, and the forms now function correctly.
Details (Give details about what this PR accomplishes, include any screenshots etc.)
My.Movie.mp4
Testing Steps (Provide details on how your changes can be tested)
Requirements
Transparency (Project board)
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
devbranch or to a feature branch, not themainbranchfix #xxx[,#xxx], where "xxx" is theissue number)
passing:
Other information: Any otherthing we need to know