Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Module integration with Rapid API framework.
Drupal core compatibility 8.x Demo page is available here http://emerap.com/en/ra/dev
The Rapid API is an API designer to the website or service.
Project page is here. Page on Packagist.
- Implementation RaConfig for Drupal 8
- Implementation Database CRUD operations
- Sub-module ra_docs for documentation view and interact
- Implementation command for drupal console
Git clone command: git clone --branch 8.x-1.x git.drupal.org:sandbox/karbunkul/2789099.git
UPD: Autocheck tools reported DrupalPractice errors but Code Sniffer DrupalPractice don't show them. And source file not contents them. How to fix errors that doesn't exist?
Comment | File | Size | Author |
---|---|---|---|
#6 | Artboard.png | 601.05 KB | karbunkul |
Screen Shot 2016-08-23 at 19.57.02.png | 66.95 KB | karbunkul |
Comments
Comment #2
karbunkul CreditAttribution: karbunkul commentedComment #3
karbunkul CreditAttribution: karbunkul commentedComment #4
karbunkul CreditAttribution: karbunkul commentedComment #5
PA robot CreditAttribution: PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpsgitdrupalorgsandboxkarbunkul2787511git
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.
Comment #6
karbunkul CreditAttribution: karbunkul commentedComment #7
karbunkul CreditAttribution: karbunkul commentedComment #8
klausiPlease don't RTBC your own issues, see the workflow: https://www.drupal.org/node/532400
Comment #9
karbunkul CreditAttribution: karbunkul commentedComment #10
PA robot CreditAttribution: PA robot commentedProject 1: https://www.drupal.org/node/2789885
Project 2: https://www.drupal.org/node/2788817
As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).
If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #11
apaderno