Paragraph UUID module extends the UUID module to manage the remote environment deployment. This will allow you to deploy paragraph_item to remote content viadeployment module

Problem Description:
When deploy content via deployment module, paragraphs_item can not be deployed due to missing entity dependency, uuid and entity service adapter. This module is created to overcome the lap between paragraphs module and deployment module.

User Guide:
1. enable paragraphs_uuid module
2. enable paragraphs_deployment module
3.configure the service endpoint to emable CURD activity for paragraphs_item entity

Sandbox Url Paragraphs UUID

git clone --branch 7.x-1.x TundraInteractive@git.drupal.org:sandbox/TundraInteractive/2369177.git paragraphs_uuid
cd paragraphs_uuid

Comments

PA robot’s picture

PA robot commented
Status: Needs review » Needs work

There are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxTundraInteractive2369...

We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)

Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).

I'm a robot and this is an automated message from Project Applications Scraper.

Tundra Interactive’s picture

Tundra Interactive commented
Status: Needs work » Needs review

Following issues are fixed
1) add README.txt
2) setup a default branch
3) remove the version number in .info file
4) correct the coding/documentation style

Some of the hook can not be avoid. We don't want make this module overweight.

hyan36’s picture

hyan36 commented
Status: Needs review » Needs work

Installed and worked for my project.

This solved my issue.

skwashd’s picture

skwashd commented

@Tundra Interactive have you proposed this as a sub module patch in the paragraphs issue queue? Many module have uuid sub modules. It is easier to maintain the functionality if the 2 modules are in the same project.

Tundra Interactive’s picture

Tundra Interactive commented
Status: Needs work » Needs review

@skwashd Thanks a lot for the review.

No, we haven't yet. We found some other extensions for this project (the paragraphs module) are done as an individual module, e.g. replicate_paragraph. On the other hand, this module does more than just implementing UUID hook. It also handles the service module and entity dependency in the same time.

Some of the modules that we are trying to support are not a part of core components e.g. entity dependency module. The rules of third party plugins may change overtime. The developers of paragraphs module may not share common interests. We figure it will be easier and cleaner to manage this module separately so that related developers/users can get more involved.

However, we are always happy to propose it as a dependent plugin to the origin project as long as the community find its necessity.

GoddamnNoise’s picture

GoddamnNoise commented

Automated Review

The automated review reports many warnings and errors.

Manual Review

Individual user account

Yes: Follows the guidelines for individual user accounts.

No duplication

Yes: Does not cause module duplication and/or fragmentation. As stated in #4, this module could be a submodule of the paragraphs module, but the developer answer in #5 explains the reasons why this should be a full module. It seems ok to me.

Master Branch

Yes: Follows the guidelines for master branch.

Licensing

Yes: Follows the licensing requirements.

3rd party assets/code

Yes: Follows the guidelines for 3rd party assets/code.

README.txt/README.md

No: Does not follow the guidelines for in-project documentation and/or the README Template.

Code long/complex enough for review

Yes: Follows the guidelines for project length and complexity.

Secure code

Yes: Meets the security requirements. It seems ok to me.

Coding style & Drupal API usage

It looks ok to me, except for the problems reported in the automated review.

Conclusion

I think it's ok when the problems detected in the automated review and the README.txt problems are solved.

GoddamnNoise’s picture

GoddamnNoise commented
Status: Needs review » Needs work
PA robot’s picture

PA robot commented
Status: Needs work » Closed (won't fix)

Closing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).

I'm a robot and this is an automated message from Project Applications Scraper.