Conversation
…ry merge, cache race, locale/region)
- Merge Odin dictionary with Studio prefetch; prefer external on key clash
- Treat empty {} as no external dict in fragment-client; tighten replace init
- Align preview dictionary locale with Store.localeOrRegion(); reload on region
- Fragment editor: surface from path, region sync for variations, init order
- Preview store: stay unresolved until placeholders exist
- Router: do not clear region override on fragment editor hash sync
- aem-fragment: after fetch, prefer cache entry if add() was a no-op
- Forward immediate flag from SourceFragmentStore.resolvePreviewFragment
…dictionary merge, cache race, locale/region)" This reverts commit edb4791.
This reverts commit 4c1e9ff.
|
Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch.
Commits
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #748 +/- ##
==========================================
+ Coverage 87.33% 87.35% +0.01%
==========================================
Files 210 210
Lines 62870 62870
==========================================
+ Hits 54908 54918 +10
+ Misses 7962 7952 -10 see 5 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
c49045c to
7e76079
Compare
npeltier
left a comment
There was a problem hiding this comment.
thanks a lot @seanchoi-dev that looks much better, one additional thing, though:
if you look at getRequestInfos, it is the async promise a lot of initial requests are pending on to start, among which the dictionary id, and settings id requests we want to start ASAP.
"problem" with this is that you add default variation fetch to that processing which may increase overall time of the pipeline when nothing is cached.
i think as soon as you get initial fragment fetch, so called requestsInfos should be available to other init method. So probably you should encapsulate the default fragment fetch in that first promise
npeltier
left a comment
There was a problem hiding this comment.
thanks ! looks better, we are getting close to it.
- we need defaultLanguage
Variationto be a proper transformer (name and init/process), - there should be no duplicated logic in customize, no need to call default language as it has already been requested
npeltier
left a comment
There was a problem hiding this comment.
lgtm @seanchoi-dev :-) thanks for the patience
please make sure you get 100% coverage and i'm good
|
Hi @seanchoi-dev , can you add better coverage |
|
@seanchoi-dev one of the jira requirements was to fix the placeholder also in studio. That part is not fixed. I still see FR placeholder on CH variation |



Resolves https://jira.corp.adobe.com/browse/MWPW-189894
QA Checklist: https://wiki.corp.adobe.com/display/adobedotcom/M@S+Engineering+QA+Use+Cases
Please do the steps below before submitting your PR for a code review or QA
🧪 Nala E2E Tests
Nala tests run automatically when you open this PR.
To run Nala tests again:
run nalalabel to this PR (in the right sidebar)To stop automatic Nala tests:
run nalalabelTest URLs:
More Test URLs: