Files
iTop/js
Stephen Abello ceba1ad1e9 N°7157 - Allow users to unsubscribe from notification channels (#611)
* N°7157 - Allow users to unsubscribe from notification channels

* Fix type hinting

* Add missing dict entries

* Allows to subscribe/unsubscribe from notifications individually

* Refactor NotificationsService to singleton pattern

* Refactor NotificationsRepository to singleton pattern and rename methods to a more functional naming

* Add PHPDoc and type hints

* Dump autoloaders

* Replace modals with toasts

* Add dict entry

---------

Co-authored-by: Molkobain <lajarige.guillaume@free.fr>
2024-02-19 09:25:47 +01:00
..
2019-10-30 10:11:33 +01:00
2024-02-09 11:18:23 +01:00
2023-03-17 18:28:47 +01:00
2023-03-17 18:28:47 +01:00
2023-03-17 18:28:47 +01:00
2023-03-17 18:28:47 +01:00
2023-03-17 18:28:47 +01:00
2023-03-17 18:28:47 +01:00
2021-03-01 11:44:37 +01:00
2023-03-17 18:28:47 +01:00
2023-03-17 18:28:47 +01:00
2023-03-17 18:28:47 +01:00
2021-08-16 11:24:58 +02:00
2023-03-17 18:28:47 +01:00
2023-03-17 18:28:47 +01:00
2024-02-15 17:14:15 +01:00
2014-11-07 13:25:37 +00:00
2024-02-09 12:04:21 +01:00
2023-03-17 18:28:47 +01:00
2023-03-17 18:28:47 +01:00
2023-03-17 18:28:47 +01:00
2023-03-17 18:28:47 +01:00
2023-03-17 18:28:47 +01:00

JS for iTop

File location

In order to better separate our developments from the embedded third-party libs, files should be moved in either the /js/components, /lib, /node_modules folders.

IMPORTANT: Before moving a file, we should first consider if:

  • The file is used in an iTop extension that should be compatible with the iTop version currently under developments
  • The file is still used in iTop itself (or if we can consider removing it for clean up)

Leading semicolon

When concataining 2 files with code execution, we might have a prb.

For example :

// file A
(A)()
// file B
(B)()

Having (A)()(B)() is different than (A)();(B)(); !

To avoid those problems simply add a leading semicolon on all JS files.

See : https://stackoverflow.com/a/23056287 3959ed505b