There should be a central place/file that contains all necessary functionalities (i.e. CRUD support). This should/could be similar to the implementations within the other BEXIS2 UI projects. In general, each of those projects contain several Service.ts files which contain/implement that functions. Please check out some of that projects to get an idea of "how to implement it...".
BEXIS2 Web Shell UI Services - within the directory, you will find services related to settings and versions (for different website parts - database, workspace, site).
In your case, the service class should implement all necessary functions related to entries and notes. Also, it makes much more sense to get started with the creation and continue with retrieval and deletion. Otherwise, you would need to mock existing entries to get/retrieve them. But in general, the services need to contain/support the following methods/functions:
Entry
[x] get (all) entries
[x] get an entry by its identifier
[x] add/create an entry
[ ] update an entry
[ ] delete/remove an entry
Note
[ ] get (all) notes
[ ] get (all) notes that belong to a specific entry (get notes by its entry identifier)
[ ] add a note
[ ] update a note
[ ] delete/remove a note
e.g., messageStore.update((storedMessages: Message[]) => [...storedMessages, newMessage]); -> move to central file
In addition, please choose and use appropriate parameters for the different implementations. E.g., there could be support of primitive parameters (int, string,...) or complex objects.
There should be a central place/file that contains all necessary functionalities (i.e. CRUD support). This should/could be similar to the implementations within the other BEXIS2 UI projects. In general, each of those projects contain severalService.ts files which contain/implement that functions. Please check out some of that projects to get an idea of "how to implement it...".
BEXIS2 Web Shell UI Services - within the directory, you will find services related to settings and versions (for different website parts - database, workspace, site).
In your case, the service class should implement all necessary functions related to entries and notes. Also, it makes much more sense to get started with the creation and continue with retrieval and deletion. Otherwise, you would need to mock existing entries to get/retrieve them. But in general, the services need to contain/support the following methods/functions:
Entry
Note
e.g., messageStore.update((storedMessages: Message[]) => [...storedMessages, newMessage]); -> move to central file
In addition, please choose and use appropriate parameters for the different implementations. E.g., there could be support of primitive parameters (int, string,...) or complex objects.