Ruben Bimberg authored 3 years ago and Klaus-Dieter Quibeldey-Cirkel committed 3 years ago

There was a problem when the
topic requirement was active, you could not
see that it was really active.

There was a problem when the
topic requirement was active, you could not
see that it was really active.

Ruben Bimberg authored 3 years ago and Klaus-Dieter Quibeldey-Cirkel committed 3 years ago

[Ticket: #143]

[Ticket: #143]

This commit ensures that the tag cloud administration window is updated
when the blacklist or profanity list is updated. This will apply the new
settings directly.

Closes #5

Also improved performance.

[Ticket: #109]

The keyword update function has a runtime that is quadratic
to the number of keywords, since the function examines all
keywords and has to search all previous keywords each time.
This commit ensures that this function is called only once
in ngOnInit instead of three times previously, as the
additional calls are redundant, reducing the administration
call time to one-third.

Closes #119

fix updating the comments after adding words to the profanity list; storage profanitylist in localstorage as a json

adds specific notification for adding and removing words to and from blacklist; fixes toLowerCase console error

Carelle Djuffo Nzangue authored 3 years ago and Klaus-Dieter Quibeldey-Cirkel committed 3 years ago

[Ticket: #97]