-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/weos 1125 - As a developer I should be able to delete a field from a content type #86
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
feature/Weos 1328: Refactor Migrate function
… skip after merge
atoniaw
changed the title
Feature/weos 1125
Feature/weos 1125 - As a developer I should be able to delete a field from a content type
Feb 8, 2022
WEOS:1328 uncommented projections test
akeemphilbert
requested changes
Feb 8, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove tests.db and tasks.db and update gitignore
Aidan-E
suggested changes
Feb 9, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"id" field is not displayed when creating a blog.
removed sending swagger schema into the migrate function fixed bug in content_entity toMap function that omits added id
used constants for database modifiers in the swagger file updated gitignore
feat:Weos 1309 Removed swagger schema parameter from projections migrate
…mber is inputted when viewing
Weos 1288 - Make 404 error if user inputs 0 when viewing item by sequence number
akeemphilbert
previously approved these changes
Feb 11, 2022
akeemphilbert
previously approved these changes
Feb 14, 2022
Aidan-E
previously approved these changes
Feb 14, 2022
akeemphilbert
approved these changes
Feb 14, 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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
* Allows a user to soft remove a database column
* Allows a user to remove a database column using x-remove
* Allows user to remove a primary key field (sqlite only)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: