Skip to content

Commit 72d9bc8

Browse files
author
Anmol Binani
committed
remove bold font for sub-item heading
1 parent 039deca commit 72d9bc8

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

README.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -6,18 +6,18 @@ The `@cap-js/notifications` package is a [CDS plugin](https://cap.cloud.sap/docs
66
- [Setup](#setup)
77
- [Usage](#usage)
88
- [Update Notification Configuration](#update-notification-configuration)
9-
- [**Notification Types Path**](#notification-types-path)
10-
- [**Notification Type Prefix**](#notification-type-prefix)
9+
- [Notification Types Path](#notification-types-path)
10+
- [Notification Type Prefix](#notification-type-prefix)
1111
- [Add Notification Types](#add-notification-types)
1212
- [Add code to send notifications](#add-code-to-send-notifications)
13-
- [**Simple Notification with title**](#simple-notification-with-title)
14-
- [**Simple Notification with title and description**](#simple-notification-with-title-and-description)
15-
- [**Custom Notifications**](#custom-notifications)
13+
- [Simple Notification with title](#simple-notification-with-title)
14+
- [Simple Notification with title and description](#simple-notification-with-title-and-description)
15+
- [Custom Notifications](#custom-notifications)
1616
- [Sample Application with notifications](#sample-application-with-notifications)
17-
- [**In Local Environment**](#in-local-environment)
17+
- [In Local Environment](#in-local-environment)
1818
- [**In Production Environment**](#in-production-environment)
1919
- [**Notification Destination**](#notification-destination)
20-
- [**Integrate with SAP Build Work Zone**](#integrate-with-sap-build-work-zone)
20+
- [Integrate with SAP Build Work Zone](#integrate-with-sap-build-work-zone)
2121
- [Contributing](#contributing)
2222
- [Code of Conduct](#code-of-conduct)
2323
- [Licensing](#licensing)
@@ -42,11 +42,11 @@ In this guide, we use the [Incidents Management reference sample app](https://gi
4242

4343
<img width="1300" alt="Default Notification config" style="border-radius:0.5rem" src="_assets/packageJsonConfig.gif">
4444

45-
#### **Notification Types Path**
45+
#### Notification Types Path
4646

4747
When you run `cds add notifications`, it will add `notificationstype.json` file with template for a notification type in the project root folder. You can add the notification types in the `notificationtype.json` file for sending the custom notification types.
4848

49-
#### **Notification Type Prefix**
49+
#### Notification Type Prefix
5050

5151
To make notification types unique to the application, prefix is added to the type key. By default, `application name` is added as the prefix. You can update the `prefix` if required.
5252

@@ -83,7 +83,7 @@ In the handler files, connect to the notifications plugin by:
8383
const alert = await cds.connect.to('notifications');
8484
```
8585

86-
#### **Simple Notification with title**
86+
#### Simple Notification with title
8787
You can use the following signature to send the simple notification with title
8888
```js
8989
alert.notify({
@@ -92,7 +92,7 @@ alert.notify({
9292
title: "New incident is reported!"
9393
});
9494
```
95-
#### **Simple Notification with title and description**
95+
#### Simple Notification with title and description
9696
You can use the following signature to send the simple notification with title and description
9797
```js
9898
alert.notify({
@@ -102,7 +102,7 @@ alert.notify({
102102
description: "Incident titled 'Engine overheating' created by 'customer X' with priority high is assigned to you!"
103103
});
104104
```
105-
#### **Custom Notifications**
105+
#### Custom Notifications
106106
You can use the following signature to send the custom notification with pre-defined notification types.
107107
```js
108108
alert.notify({
@@ -131,7 +131,7 @@ alert.notify({
131131

132132
### Sample Application with notifications
133133

134-
#### **In Local Environment**
134+
#### In Local Environment
135135
In local environment, when you publish notification, it is mocked to publish the nofication to the console.
136136

137137
<img width="1300" alt="Notify to console" style="border-radius:0.5rem;padding:1rem;background:rgb(24 24 24)" src="_assets/notifyToConsole.png">
@@ -142,7 +142,7 @@ In local environment, when you publish notification, it is mocked to publish the
142142

143143
As a pre-requisite to publish the notification, you need to have a [destination](https://help.sap.com/docs/build-work-zone-standard-edition/sap-build-work-zone-standard-edition/enabling-notifications-for-custom-apps-on-sap-btp-cloud-foundry#configure-the-destination-to-the-notifications-service) configured to publish the notification. In the `package.json` by default destination name `SAP_Notification` is added, you can modify the destination name that you are configuring.
144144

145-
##### **Integrate with SAP Build Work Zone**
145+
##### Integrate with SAP Build Work Zone
146146

147147
Once application is deployed and [integrated with SAP Build Work Zone](https://github.com/cap-js/calesi/tree/main/samples/notifications), you can see the notification under fiori notifications icon!
148148

0 commit comments

Comments
 (0)