[MGNLREST-732] Tune default configuration of jcrPagesDeliveryEndpoint_v2 Created: 13/Jun/23 Updated: 15/Jun/23 Resolved: 15/Jun/23 |
|
| Status: | Closed |
| Project: | Magnolia REST Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| 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)
|
||||||||||||||||
| Team: | |||||||||||||||||
| Description |
|
I would like to review the default configuration of jcrPagesDeliveryEndpoint_v2 to ensure the best developer experience.
Context: We introduced Default properties has been set to jcrPagesDeliveryEndpoint_v2 by default I would like to do performance tests of inheritanceComponent and autogenerateComponent to determine how much of an impact they have, because it would be easier for a developer if they were on by default instead of off by default. |
| Comments |
| Comment by Christopher Zimmermann [ 15/Jun/23 ] |
|
It turns ou this has already been taken care of. There is no need to specify those properties. |