Provide a narrative description of what you are trying to accomplish:
[ ] Are you fixing a bug?
[ ] Detail how the bug is invoked currently.
[ ] Detail the original, incorrect behavior.
[ ] Detail the new, expected behavior.
[ ] Base your feature on the master branch, and submit against that branch.
[ ] Add a regression test that demonstrates the bug, and proves the fix.
[ ] Add a CHANGELOG.md entry for the fix.
[ ] Are you creating a new feature?
[ ] Why is the new feature needed? What purpose does it serve?
[ ] How will users use the new feature?
[ ] Base your feature on the develop branch, and submit against that branch.
[ ] Add only one feature per pull request; split multiple features over multiple pull requests
[ ] Add tests for the new feature.
[ ] Add documentation for the new feature.
[ ] Add a CHANGELOG.md entry for the new feature.
[ ] Is this related to quality assurance?
[X] Is this related to documentation?
This change documents the ContinueIfEmpty annotation in the annotation section of the quick-start guide. I know that ContinueIfEmpty is deprecated, but in version 2, from experience, it's still required for fields that are not set as required. Given that, I'm documenting it to help others avoid the confusion that I encountered.
froschdesign
commented
5 years ago
Provide a narrative description of what you are trying to accomplish:
[ ] Are you fixing a bug?
masterbranch, and submit against that branch.CHANGELOG.mdentry for the fix.[ ] Are you creating a new feature?
developbranch, and submit against that branch.CHANGELOG.mdentry for the new feature.[ ] Is this related to quality assurance?
[X] Is this related to documentation?
This change documents the
ContinueIfEmptyannotation in the annotation section of the quick-start guide. I know thatContinueIfEmptyis deprecated, but in version 2, from experience, it's still required for fields that are not set as required. Given that, I'm documenting it to help others avoid the confusion that I encountered.