Fix EZP-25091: "always available" flag is hardcoded to true when creating content #68
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
|
+1 |
|
self note: just discovered that the REST API is able to handle the boolean |
|
+1 |
dpobel
added a commit
that referenced
this pull request
Nov 17, 2015
…able Fix EZP-25091: "always available" flag is hardcoded to true when creating content
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.
JIRA: https://jira.ez.no/browse/EZP-25091
Description
This patch removes the hardcoded value for the "always available" flag in the content create struct and adds a parameter to the content create struct and the
ContentService#newContentCreateStructmethod so that it's possible to set a correct value.Tests
unit test + manual test in PlatformUI