aem-react | components based on React for server and client side | Content Management System library

by sinnerschrader Java Version: 0.23.1 License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | aem-react Summary

aem-react is a Java library typically used in Web Site, Content Management System applications. aem-react has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. However aem-react has 1 bugs. You can download it from GitHub, Maven.

AEM templates and components based on React for server and client side. Provides a demo content package and core osgi bundle.

Support

Quality

Security

License

Reuse

Support

aem-react has a low active ecosystem.

It has 144 star(s) with 31 fork(s). There are 24 watchers for this library.

It had no major release in the last 12 months.

There are 20 open issues and 33 have been closed. On average issues are closed in 43 days. There are 11 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of aem-react is 0.23.1

Quality

aem-react has 1 bugs (0 blocker, 0 critical, 1 major, 0 minor) and 27 code smells.

Security

aem-react has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

aem-react code analysis shows 0 unresolved vulnerabilities.

There are 1 security hotspots that need review.

License

aem-react is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

aem-react releases are available to install and integrate.

Deployable package is available in Maven.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

It has 2825 lines of code, 108 functions and 88 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed aem-react and discovered the below as its top functions. This is intended to give you an instant insight into aem-react implemented functionality, and help decide if they suit your requirements.

Evaluates the given reader
Wraps the rendered HTML in a Tea
Renders a given react component
Renders the react markup
Get the edit dialog
Include resource
Parse an edit dialog node
Finds cities
Gets a resource
Invokes the proxied method on the target object
Checks if the given resource type is a react component
Gets a connection to the repository
Binds the dynamic class loader
Returns a JsProxy for the given class
Load JCR script

Get all kandi verified functions for this library.

aem-react Key Features

No Key Features are available at this moment for aem-react.

aem-react Examples and Code Snippets

No Code Snippets are available at this moment for aem-react.

Community Discussions

Trending Discussions on aem-react

Is it possible to use React components to author AEM Experience Fragments, which then feed a headless frontend?

QUESTION

Is it possible to use React components to author AEM Experience Fragments, which then feed a headless frontend?

Asked 2020-Sep-18 at 18:15

To briefly describe my goals --

I have an external React component library of ~70 React components, which feeds a web frontend (Websphere Commerce site, which pulls in Experience Fragments via AJAX calls to get the fragment HTML), and also a React Native app. So for the web, AEM is basically the content engine which feeds our headless frontend.
I'd like to use those same React components to feed the AEM Experience Fragment authoring experience, instead of having to rebuild each React component as an HTL template within AEM -- it's too much overhead to maintain a completely separate component library of HTL templates
By following the official Adobe tutorial here, I see how it is possible to map React components to the Content Fragment authoring experience. By which I mean, if I go to AEM Home > Sites > (my site) > create a new fragment, the component I drag in is fed by a React template. I can tell, because the markup matches what is in my BasicComponent.js React template in ui.frontend, and not the basic-component.html template in ui.apps.
But, if I go to AEM Home > Experience Fragments > create a new fragment, that same BasicComponent component will pull from the basic-component.html file in the component folder (next to .content.xml), instead of from BasicComponent.js

I'm new to AEM, so hopefully the above makes sense. I know I am missing something pretty fundamental re: how Experience Fragments differ from Content Fragments (if that is the right term). I've spent a lot of time Googling around for information, but I'm finding that my own ignorance is making it difficult for me to determine if what I'm reading is or is not a clue to solving my issue.

This is the repo that I pulled down to experiment with: https://github.com/drginm/aem-react-simple-example

Any help much appreciated! I'm sure I'm not the only AEM newbie looking for an approachable model for handling this situation.

...

ANSWER

Answered 2020-Sep-18 at 18:15

Experience Fragments is not recommended used with ajax html in headless architecture, it should be exposed via sling model exporter in json format for the react consumption.

To edit and modify the experience fragments AEM doesn't provide any APIs, AEM developer should give custom REST APIs to do the changes.

I would recommend to go with the content fragments where the CRUD operation is possible via Assets api in AEM.

References

Source https://stackoverflow.com/questions/63959128

Community Discussions, Code Snippets contain sources that include Stack Exchange Network