#535-Create-service-to-fetch-and-save-layout-config-from/to-user-database

a22erigr commented

2026-04-28 11:48:09 +00:00

Collaborator

The service contains a number of endpoints that may be used to get/fatch layouts from the database
- getSpecificLayout: Fetches specific layout
  - Requires input:
  - UserID
  - ID
- getFavoriteLayout: Gets the favorite layout of a user (lovers number in layout order)
  - Requires input:
  - UserID
- getLayoutNameAndID. Retrieves all of the Name and id
  - Requires input:
  - UserID
  - Gets: Json array
- saveSpecificLayout: saves pre existing layout
  - Requires input:
  - UserID
  - ID
  - JsonPayload (string)
  - Gets
  - Successful/fail
- saveNewLayout
- Requires input:
  - Requires input:
  - UserID
  - NameOfLayout

Tested on my computer using bruno. All of the endpoints works.
- 172.18.0.14:8080/layout/getSpecificLayout
- {
  "userID":1,
  "id": 2
  }
- 172.18.0.14:8080/layout/getFavoriteLayout?userID=2
- 172.18.0.14:8080/layout/saveSpecificLayout
- {
  "userID": 1,
  "id": 2,
  "jsonPayload": "[{"Name":"HemsidaStandard","ID":1},{"Name":"DashboardVy","D":2}]"}
- 172.18.0.14:8080/layout/saveNewLayout
- {
  "userID": 1,
  "name": "My Layout",
  "jsonPayload": "[{"Name":"HemsidaStandard","ID":1},{"Name":"DashboardVy","D":2}]"
  }
- 172.18.0.14:8080/layout/getLayoutNameAndID?userID=1

- The service contains a number of endpoints that may be used to get/fatch layouts from the database - getSpecificLayout: Fetches specific layout - Requires input: - UserID - ID - getFavoriteLayout: Gets the favorite layout of a user (lovers number in layout order) - Requires input: - UserID - getLayoutNameAndID. Retrieves all of the Name and id - Requires input: - UserID - Gets: Json array - saveSpecificLayout: saves pre existing layout - Requires input: - UserID - ID - JsonPayload (string) - Gets - Successful/fail - saveNewLayout - Requires input: - Requires input: - UserID - NameOfLayout + Tested on my computer using bruno. All of the endpoints works. + 172.18.0.14:8080/layout/getSpecificLayout + { "userID":1, "id": 2 } + 172.18.0.14:8080/layout/getFavoriteLayout?userID=2 + 172.18.0.14:8080/layout/saveSpecificLayout + { "userID": 1, "id": 2, "jsonPayload": "[{\"Name\":\"HemsidaStandard\",\"ID\":1},{\"Name\":\"DashboardVy\",\"D\":2}]"} + 172.18.0.14:8080/layout/saveNewLayout + { "userID": 1, "name": "My Layout", "jsonPayload": "[{\"Name\":\"HemsidaStandard\",\"ID\":1},{\"Name\":\"DashboardVy\",\"D\":2}]" } + 172.18.0.14:8080/layout/getLayoutNameAndID?userID=1

a22erigr added 8 commits

2026-04-28 11:48:10 +00:00

Created general service structure f26822d270

update docker compose and scripts 091337a8ac

clean up 1f22eb561e

removed artifacts that came with it after copying from loginService

Implemented Endpoint and service fcc79ea822

+ All endpoints are now created
+ Models for transporting data implemented
+ Service recive request. No logic implemented

Minor fixes to endpoints 5cda7f4858

Implemented all of the database functions 2820783454

+ All of the database functions are now implemented
  + Not tested with database but get the result "Name or service not
known" when using bruno
+ Updated the service
+ Uses more modern npgsql standard

Updated build scripts and docker yaml d0f7a296a7

Implemented layoutService 198d8b2d85

+ it is now possible to both reach all endpoints and get  desired result
+ Implemented database logic
+ Implemented the ability to fech layouts
+ Implemented the ability to save layouts
+ Implemented GetlayoutNameAndID.
  + Returns a json array containing Name and ID

a22erigr added the

needs review

label

2026-04-28 11:48:42 +00:00

a22erigr added 1 commit

2026-04-28 11:49:59 +00:00

Removed outdated unit tests fb436af0c0

a22erigr was assigned by c24elipe

2026-04-28 11:54:44 +00:00

b24erika added the

backEnd

label

2026-04-28 11:56:00 +00:00

a22erigr added 1 commit

2026-04-28 11:56:23 +00:00

Merge branch 'team_2_week_3' into #535-Create-service-to-fetch-and-save-layout-config-from/to-user-database f701f5aeda

a22erigr added 1 commit

2026-04-28 11:59:54 +00:00

fix c37126d405

a24vinla added 1 commit

2026-04-29 07:38:14 +00:00

Changed passwords 6cb3a6f7b3

b24idalu commented

2026-04-29 07:39:38 +00:00

Collaborator

Review on #523

Tested on windows using chrome

App starts.
Did not manage to figure out how to test the endpoints using bruno.

Inspected following files:

Checked all files changed
- Indendentation:
  - Follows prettier
- Naming convention:
  - Follows naming convention, some places need changes though.
- Comments:
  - Code is commented in the necessary places, though some seem like old notes or for future references.
- General code quality:
  - Code quality is generally well

What needs to be done:

/scripts/UnixRebuild.sh & /scripts/UnixRebuildDebug.sh
- The name of the docker build is "tempservice" when I assume it should be layoutService?
/service/layoutService/layoutService.Test/UnitTest1.cs
- There is an invis unicode character at the start of the file, unsure if it should be there, but code still works.
/service/layoutService/layoutService/DatabaseLogic/DatabaseQueries.cs
- Some variable names are shortened (conn could be connection or something more obvious for example)
- There are some comments that can be cleaned up
/service/layoutService/layoutService/README.md
- The readme is not updated (copy of loginservice)
/service/layoutService/layoutService/Services/LayoutService.cs
- Note saying to move line to service
/service/layoutService/layoutService/Program.cs
- The "important" line is commented out, either remove comment or uncomment
Should a test be implemented for this? And should bruno be part of the testing standard for endpoints?

Conclusion

There are some small fixes left, like renaming some variables and after that it should be ready to be merged.
Side note, but it could be good to create a wikipage with information about bruno.
Should week3 really be merged into this branch? Do not know when we merge branch into weekly and viceversa.
This was a fast review since a merge is happening soon.

### Review on #523 ### Tested on windows using chrome - App starts. - Did not manage to figure out how to test the endpoints using bruno. ### Inspected following files: - Checked all files changed - Indendentation: - Follows prettier - Naming convention: - Follows naming convention, some places need changes though. - Comments: - Code is commented in the necessary places, though some seem like old notes or for future references. - General code quality: - Code quality is generally well ## What needs to be done: - /scripts/UnixRebuild.sh & /scripts/UnixRebuildDebug.sh - The name of the docker build is "tempservice" when I assume it should be layoutService? - /service/layoutService/layoutService.Test/UnitTest1.cs - There is an invis unicode character at the start of the file, unsure if it should be there, but code still works. - /service/layoutService/layoutService/DatabaseLogic/DatabaseQueries.cs - Some variable names are shortened (conn could be connection or something more obvious for example) - There are some comments that can be cleaned up - /service/layoutService/layoutService/README.md - The readme is not updated (copy of loginservice) - /service/layoutService/layoutService/Services/LayoutService.cs - Note saying to move line to service - /service/layoutService/layoutService/Program.cs - The "important" line is commented out, either remove comment or uncomment - Should a test be implemented for this? And should bruno be part of the testing standard for endpoints? ## Conclusion There are some small fixes left, like renaming some variables and after that it should be ready to be merged. Side note, but it could be good to create a wikipage with information about bruno. Should week3 really be merged into this branch? Do not know when we merge branch into weekly and viceversa. This was a fast review since a merge is happening soon.

a24vinla added 1 commit

2026-04-29 07:45:55 +00:00

Changed name of image and removed duplicates in buildscripts 6bca1390d6