[MGNLREST-133] Check included node-types in query responses Created: 25/Oct/17 Updated: 31/Oct/17 Resolved: 30/Oct/17 |
|
| Status: | Closed |
| Project: | Magnolia REST Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.0 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Sang Ngo Huu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 3d 2.5h | ||
| Original Estimate: | 2d | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: | |
| Epic Link: | REST Queries |
| Sprint: | Saigon 119 |
| Story Points: | 5 |
| Description |
We first verify whether these statements are correct. Then we should probably consider splitting nodeTypes config into primaryNodeTypes vs. secondaryNodeTypes (or maybe some other property-based flavor of config). With this, developers would get more clarity about what to expect in responses. See also |
| Comments |
| Comment by Dai Ha [ 30/Oct/17 ] |
|
verify with build: magnolia-community-demo-bundle-5.6-20171030.075022-164-tomcat-bundle.zip |