Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in
Toggle navigation
Menu
Open sidebar
Notifications project
web-portal
Commits
88b8de4f
Commit
88b8de4f
authored
Apr 25, 2022
by
Carina Antunes
Browse files
remove debug logs
parent
93263f0b
Pipeline
#3889915
passed with stages
in 8 minutes and 53 seconds
Changes
4
Pipelines
2
Hide whitespace changes
Inline
Side-by-side
README.md
View file @
88b8de4f
...
...
@@ -27,3 +27,18 @@ docker run -p 3000:3000 web-portal
## Testing locally push registration
Push registration requires SSL and a valid cert, even on localhost.
## Troubleshooting
### sass build error on master
```
/usr/src/app/node_modules/node-sass/lib/binding.js:13
throw new Error(errors.unsupportedEnvironment());
^
Error: Node Sass does not yet support your current environment: Linux/musl 64-bit with Unsupported runtime (88)
```
Solution:
```
npm uninstall node-sass-chokidar && npm install node-sass-chokidar
```
src/about/components/AboutContact.js
View file @
88b8de4f
...
...
@@ -15,7 +15,7 @@ const AboutContact = () => {
The
service
is
provided
by
IT
-
CDA
-
WF
section
and
is
part
of
the
MALT
activities
as
replacement
option
for
mailing
lists
.
<
/p
>
<
p
>
Report
any
issues
or
question
at
our
Mattermost
channel
:
<
/p
>
<
p
>
Report
any
issues
or
question
s
at
our
Mattermost
channel
or
Service
Now
:
<
/p
>
<
a
href
=
"
https://mattermost.web.cern.ch/it-dep/channels/notifications
"
target
=
"
_blank
"
...
...
@@ -23,6 +23,15 @@ const AboutContact = () => {
>
https
:
//mattermost.web.cern.ch/it-dep/channels/notifications
<
/a
>
<
br
/>
<
br
/>
<
a
href
=
"
https://cern.service-now.com/service-portal?id=functional_element&name=notifications
"
target
=
"
_blank
"
rel
=
"
noopener noreferrer
"
>
Service
Now
<
/a
>
<
/Container
>
);
};
...
...
src/about/components/AboutNotifications.js
View file @
88b8de4f
...
...
@@ -47,7 +47,19 @@ const AboutNotifications = () => {
<
List
.
Item
>
Normal
<
/List.Item
>
<
List
.
Item
>
Important
<
/List.Item
>
<
List
.
Item
>
[
Blocked
]
Critical
(
Only
allowed
for
very
specific
channels
after
approval
)
[
Blocked
]
Critical
<
br
/>
Only
allowed
for
very
specific
channels
after
approval
.
Critical
notifications
bypass
all
preferences
and
are
targeted
to
all
users
on
all
available
devices
.
Available
after
approval
,
request
via
{
'
'
}
<
a
href
=
"
https://cern.service-now.com/service-portal?id=sc_cat_item&name=request&fe=notifications
"
target
=
"
_blank
"
rel
=
"
noopener noreferrer
"
>
ticket
<
/a
>
.
<
/List.Item
>
<
/List
>
<
/List.Description
>
...
...
@@ -132,23 +144,6 @@ const AboutNotifications = () => {
the
user
is
not
,
indeed
,
member
of
the
channel
,
the
user
will
not
be
notified
.
<
/p
>
<
p
>
Example
:
The
channel
<
code
>
Windows
<
/code> is used to announce patches, news
,
etc
.
to
the
Windows
users
at
CERN
.
For
this
reason
,
members
of
grappa
group
{
'
'
}
<
code
>
windows
<
/code> have been added to this channel when it was created an
d
are
part
of
it
now
.
A
new
patch
for
Windows
11
will
be
lunched
tomorrow
,
and
channel
admins
want
to
notify
only
the
concerned
users
(
<
code
>
windows11
<
/code>{' '
}
grappa
group
members
that
belong
to
the
channel
).
By
adding
the
{
'
'
}
<
code
>
windows11
<
/code> grappa group as a grappa group to send a direc
t
notification
,
only
these
members
of
the
channel
will
be
notified
,
so
Windows
10
and
Windows
Server
users
that
are
on
the
channel
will
not
get
the
notification
.
If
for
example
the
notification
concerns
now
to
Windows
10
and
Windows
11
users
,
by
adding
<
code
>
windows10
<
/code> and <code>windows11</
code
>
{
'
'
}
grappa
groups
as
grappa
groups
to
send
direct
notification
will
notify
members
of
both
grappa
groups
that
are
members
of
the
channel
,
excluding
{
'
'
}
<
code
>
windows
-
server
<
/code> members of the channel. If for some reason, extr
a
single
users
are
required
,
it
is
possible
to
add
them
by
specifying
these
users
by
their
emails
or
logins
,
so
apart
from
the
previous
users
reached
,
these
single
users
will
be
also
notified
ONLY
if
they
are
part
of
the
channel
.
<
Image
src
=
{
`
${
process
.
env
.
PUBLIC_URL
}
images/about_images/venn_diagram.png`
}
size
=
"
medium
"
...
...
@@ -163,12 +158,12 @@ const AboutNotifications = () => {
<
br
/>
When
to
use
each
mode
?
<
br
/>
<
code
>
Intersection
between
specified
users
or
groups
and
channel
members
<
/code>
mod
e
is
useful
to
notify
a
subset
of
users
from
a
channel
,
while
<
code
>
to
all
specified
users
or
groups
<
/code>
can be used if you want to make sur
e
that
the
notification
reaches
everyone
and
you
may
be
not
sure
if
they
are
on
the
channel
yet
,
or
want
to
automate
the
process
of
adding
users
to
a
channel
dynamically
while
sending
notifications
.
<
b
>
Intersection
<
/b>
between specified users or groups and channel members mode
i
s
useful
to
notify
a
subset
of
users
from
a
channel
,
while
<
b
>
to
all
<
/b>
specified users or groups can be used if you want to make sure
tha
t
the
notification
reaches
everyone
and
you
may
not
be
sure
if
they
are
on
the
channel
yet
,
or
if
you
want
to
automate
the
process
of
adding
users
to
a
channel
dynamically
while
sending
notifications
.
<
br
/>
<
/List.Description
>
<
/List.Item
>
...
...
src/notifications/components/SendNotificationComponent/SendNotificationComponent.js
View file @
88b8de4f
...
...
@@ -440,7 +440,6 @@ const SendNotificationComponent = ({
<
CKEditor
dispatchEvent
=
{
dispatch
}
type
=
"
classic
"
debug
data
=
{
editorData
}
uniqueName
=
"
body-editor
"
/>
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment