You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It acts as an interface between client and the scheduling services provided, allowing users to interact for consultation with specialists. It also provides the info of availability and unavailability of specialists, retrieving available slots for specialists, booking and cancelling slots, and fetching day views of specialists for a particular specialization.
5
5
@@ -12,7 +12,7 @@ It acts as an interface between client and the scheduling services provided, all
12
12
This microservice is built on Java, Spring boot framework and MySQL DB.
13
13
14
14
### Prerequisites
15
-
* JDK 1.8
15
+
* JDK 17
16
16
* Wildfly (or any compatible app server)
17
17
* Redis
18
18
* MySQL Database
@@ -34,6 +34,49 @@ To install the MMU module, please follow these steps:
34
34
## Usage
35
35
All features have been exposed as REST endpoints. Refer to the SWAGGER API specification for details.
36
36
37
+
## Setting Up Commit Hooks
38
+
39
+
This project uses Git hooks to enforce consistent code quality and commit message standards. Even though this is a Java project, the hooks are powered by Node.js. Follow these steps to set up the hooks locally:
40
+
41
+
### Prerequisites
42
+
- Node.js (v14 or later)
43
+
- npm (comes with Node.js)
44
+
45
+
### Setup Steps
46
+
47
+
1.**Install Node.js and npm**
48
+
- Download and install from [nodejs.org](https://nodejs.org/)
49
+
- Verify installation with:
50
+
```
51
+
node --version
52
+
npm --version
53
+
```
54
+
2. **Install dependencies**
55
+
- From the project root directory, run:
56
+
```
57
+
npm ci
58
+
```
59
+
- This will install all required dependencies including Husky and commitlint
60
+
3. **Verify hooks installation**
61
+
- The hooks should be automatically installed by Husky
62
+
- You can verify by checking if the `.husky` directory contains executable hooks
63
+
### Commit Message Convention
64
+
This project follows a specific commit message format:
65
+
- Format: `type(scope): subject`
66
+
- Example: `feat(login): add remember me functionality`
67
+
Types include:
68
+
- `feat`: A new feature
69
+
- `fix`: A bug fix
70
+
- `docs`: Documentation changes
71
+
- `style`: Code style changes (formatting, etc.)
72
+
- `refactor`: Code changes that neither fix bugs nor add features
73
+
- `perf`: Performance improvements
74
+
- `test`: Adding or fixing tests
75
+
- `build`: Changes to build process or tools
76
+
- `ci`: Changes to CI configuration
77
+
- `chore`: Other changes (e.g., maintenance tasks, dependencies)
78
+
Your commit messages will be automatically validated when you commit, ensuring project consistency.
79
+
37
80
## Filing Issues
38
81
39
82
If you encounter any issues, bugs, or have feature requests, please file them in the [main AMRIT repository](https://github.com/PSMRI/AMRIT/issues). Centralizing all feedback helps us streamline improvements and address concerns efficiently.
0 commit comments