Update fields.js bugfix 'no sentiment' #357
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
Added no sentiment option for the field, so that it will be send correctly to the api. Belongs to bug https://trello.com/c/URra6zQt
nlsvgtr
approved these changes
Sep 19, 2022
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.
Description
Made it possible for arguments with 'no sentiment' to be added to the databases
REQUIRES openstad/openstad-api#244 to work, if this one is not available then the API will reject the value send by this fix.
Issue reference
Fixes # (issue)
Belongs to bug https://trello.com/c/URra6zQt
Type of change
bugfix (wrong branchname, by accident)
Tests
Branch
devel