Download the PHP package rebelcode/rcmod-wp-bookings-ui without Composer
On this page you can find all versions of the php package rebelcode/rcmod-wp-bookings-ui. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download rebelcode/rcmod-wp-bookings-ui
More information about rebelcode/rcmod-wp-bookings-ui
Files in rebelcode/rcmod-wp-bookings-ui
Package rcmod-wp-bookings-ui
Short Description A RebelCode module that provides the WordPress admin interface for bookings.
License GPL-3.0
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package rcmod-wp-bookings-ui
RebelCode - WP Bookings UI Module
WP Bookings plugin's UI Module
Run Front Assembling
To run front assembling just run:
Run Application
This module's front-end logic expects to retrieve initial application state to initialize application. By default it is window.EDDBK_APP_STATE which should be generated on server using wp_localize_script(...).
We have two separate pages that require different states to work. Bookings page and one service page. So for this 2 pages we need two different application states.
Service Page
State
Expected structure of state on service page (when user open some service for editing):
Bookings Page
State
Expected structure of state on bookings page:
Endpoints
Here is endpoints required for bookings page. Paths are not real, this is just demonstration of concept which functionality is required from backend to make everything works.
Bookings
GET /booking - Retrieve list of bookings, screen statuses list with items count for each status, filtered items count. It should accept next parameters to filter result:
Both views:
search- Search string to filter bookings by it. Allows to filter bookings via client name or client email address. If empty - no searching happens. For example:[email protected],service- Service to filter by it. If empty - no service filtering happens. For example:1,statuses- Enabled screen statues to filter bookings by them. For example:draft,scheduled,status- Current status to filter. For example:allordraft.
Calendar filtering:
start- Start date to get bookings. For example:"2017-07-11",end- End date to get bookings. For example:"2017-07-18".
List view filtering:
page- Page number for pagination. For exmple:1,month- Month number to filter bookings by it. If empty - no month filtering happens. For example:1.
POST /booking - Create one booking.
UPDATE /booking/{id} - Update booking by it's ID.
DELETE /booking/{id} - Delete booking by it's ID.
Clients
This API endpoint is required for booking editing functionality. When user creates/edits booking he can search across all clients or create new one.
GET /client?search={queryString} - Search for client.
POST /client - Create new client. Should accept this two fields:
name- Client's name,email- Clien's email.
All versions of rcmod-wp-bookings-ui with dependencies
rebelcode/modular Version ^0.1-alpha1
dhii/normalization-helper-base Version ^0.1-alpha2
dhii/placeholder-template Version ^0.1-alpha2
dhii/memoize-memory Version ^0.2-alpha1
rebelcode/transformers Version ^0.1-alpha1