since
15-01-2021
Level 1
Re: Why React example does not use Async call to fetch js...
sumantap8752196
- Adobe Experience Manager
332
0
1
sumantap8752196
I do not understand why you guys accept wrong answer as correct
answer!!!!! crazy
Views
Likes
Replies
Re: Why React example does not use Async call to fetch js...
sumantap8752196
- Adobe Experience Manager
322
0
0
sumantap8752196
thanks, yes i know
Views
Likes
Replies
Why React example does not use Async call to fetch json of requested page
sumantap8752196
- Adobe Experience Manager
594
0
4
sumantap8752196
I am following this tutorials:
https://github.com/adobe/aem-sample-we-retail-journalHere, all the child
pages JSON is stored into __INITIAL_STATE__ id. I want to know why it is
done in this way, can someone please explain?Instead what if I navigate
on different links and then on click of each links if I call model json
of that page via Async fetch and then accordingly set __INITIAL_STATE__
id. What problem in this approach?
Views
Likes
Replies
Re: AEM SPA Routing Issues with hash and query parameter
sumantap8752196
- Adobe Experience Manager
2.8K
0
0
sumantap8752196
that code is just in React, but how React component is populating
myurl? there must be some React component State properties which is read
, check that code, also when you say autometically, there must be some
code on componentDidMount() which triggers async call. Sorry without
your further code I cannot help you.
Views
Likes
Replies
Re: AEM SPA Routing Issues with hash and query parameter
sumantap8752196
- Adobe Experience Manager
2.8K
0
0
sumantap8752196
this issue comes when first time page load or after page is loaded then
when you navigate between links? It seems you have custom code to call
model.json on every link click, it could be issue with react component
state is not updated correctly, so if you post your code then will be
better to upderstand
Views
Likes
Replies
Re: AEM SPA Routing Issues with hash and query parameter
sumantap8752196
- Adobe Experience Manager
2.8K
0
0
sumantap8752196
Understood, are you using Adobe SDK or own to call model? if Adobe SDK
then can you check what is the value of cq:pagemodel_root_url when you
have this error, ideally it should have yourUrl.model.json and then
React code reads it from there
Views
Likes
Replies
Re: AEM SPA Routing Issues with hash and query parameter
sumantap8752196
- Adobe Experience Manager
2.8K
0
0
sumantap8752196
So you are using extension less url ? and without looking at your Apache
rewriter rule, it is difficult to say whats wrong in the rule
Views
Likes
Replies
Re: AEM SPA Routing Issues with hash and query parameter
sumantap8752196
- Adobe Experience Manager
2.9K
0
0
sumantap8752196
Is this Client or Server Side react?
Views
Likes
Replies
SPA Server Side approach
sumantap8752196
- Adobe Experience Manager Forms
1.1K
1
2
sumantap8752196
I am evaluating how is it possible to implement Server Side Rendering in
SPA app with React and AEM as content service. This is the approach I
see Next.js suggest to have per-rendered and all most all CMS system
suggests: 1. User request a page from react app running on Node server2.
Node server requests JSON data from CMS through fetch call3. Then React
App reads this JSON and transform HTML into String like renderToString()
and sends the response back to the user. The disadvantage of this
appr...
Views
Like
Replies
Advantage of Adobe I/O runtime
sumantap8752196
- Adobe I/O Runtime
3.1K
0
1
sumantap8752196
Hello,I am exploring the option of developing Server Side React App with
Adobe I/O runtime as described here :
https://docs.adobe.com/content/help/en/experience-manager-64/developing/headless/spas/spa-ssr.htmlI
know the advantage of using Serverless technology but I do not
understand the real benefit of using SSR app deployed in Adobe I/O. Ad
sated in that page the advantage is "More familiar to SPA developers".
Is this the only advantage? Can you please help me to understand, any
link?
Views
Likes
Replies
