Andras/BoundlessFlowCampus2K
3
6
Fork 0
Code Issues 143 Pull requests 14 Projects Releases Packages Wiki Activity Actions 2

737 Parking restructure re-branch #892

Merged
a24julot merged 11 commits from 737-Parking-restructure-re-branch into team_1_week_5 2026-05-12 08:23:09 +00:00
Conversation 4 Commits 11 Files changed 29 +610 -296
a24timsv commented 2026-05-11 12:23:14 +00:00
Collaborator
Copy link

A restructure of the original Parking API. Now simulates the existing parking spots on campus with its special attributes (charging, disabled and reserved). The refresh time for the spot is 30 seconds as of now (can be changed in the read folder). It currently only sends data accessible to the frontend, which you find in its Wiki page. The next step is to add frontend components for the data.

A restructure of the original Parking API. Now simulates the existing parking spots on campus with its special attributes (charging, disabled and reserved). The refresh time for the spot is 30 seconds as of now (can be changed in the read folder). It currently only sends data accessible to the frontend, which you find in its [Wiki page](https://git.webug.se/Andras/BoundlessFlowCampus2K/wiki/Parking-endpoints). The next step is to add frontend components for the data.
Needed to move everything from one branch to another, thus the large commit
Added the parkingService to the entrypoint and build script (Windows)
Now the service can contact the DB and retrieve data (yippie).
Also added an endpoint that gives info on a specific spot
Now all endpoints deliver the correct data, also added an endpoint to view all available zones (for dropdown or similar)
Wrote the README and did some cleanup in SpotGenerator
Added a new endpoint that shows special spots, with the attributes charging, disabled and reserved.
Went outside (woah) and checked what all spots have for attributes.
Removed unused code and comments that are not necessary
Added parkingService components to the installation and build scripts
a24julot 2026-05-11 12:29:10 +00:00
a24sakma commented 2026-05-11 13:39:43 +00:00
Collaborator
Copy link

The frontend api endpoints seems to be broken maybe ngnx. In the useParking.js file remove the api from the url the it should work :)

The frontend api endpoints seems to be broken ~~maybe ngnx~~. In the useParking.js file remove the api from the url the it should work :)
Screenshot from 2026-05-11 15-30-17.png
63 KiB
Screenshot from 2026-05-11 15-30-17.png
a24sakma requested changes 2026-05-11 14:06:30 +00:00
generateMockup/parkingMockup/parkingApiMockup/Program.cs Outdated
@ -112,2 +24,3 @@
};
var data = zones;
return Results.Json(data);
a24sakma commented 2026-05-11 13:54:08 +00:00
Collaborator
Copy link

you don't need row 24 for creation of data variable. You can directly return Results.Json(zones)

you don't need row 24 for creation of data variable. You can directly return `Results.Json(zones)`
a24timsv commented 2026-05-12 07:33:17 +00:00
Author
Collaborator
Copy link

Agreed, I added it mostly because other mockups was returning a data variable. I'll just return the zones instead, maybe making it easier to read.

Agreed, I added it mostly because other mockups was returning a data variable. I'll just return the zones instead, maybe making it easier to read.
a24sakma marked this conversation as resolved
service/parkingService/parkingService/DatabaseLogic/DatabaseQueries.cs
@ -0,0 +18,4 @@
return result;
}
public async Task<IEnumerable<ParkingData?>> FetchZoneLatest(string zoneCode)
a24sakma commented 2026-05-11 14:00:03 +00:00
Collaborator
Copy link

I don't think you need latest in the end of FetchZone.
For temperature and energy it makes sense because we want latest temperature or energy right. but not for parking. What do you think?

I have seen it is used everywhere if it is a lot of effort then we can skip it.

I don't think you need latest in the end of FetchZone. For temperature and energy it makes sense because we want latest temperature or energy right. but not for parking. What do you think? I have seen it is used everywhere if it is a lot of effort then we can skip it.
a24timsv commented 2026-05-12 07:31:08 +00:00
Author
Collaborator
Copy link

The latest suffix refers to that the method returns the spot information with the latest timestamps, as updates to a spot doesn't directly delete entries in the database it needs to fetch the latest data for the representation to be "now", so to speak.

The latest suffix refers to that the method returns the spot information with the latest timestamps, as updates to a spot doesn't directly delete entries in the database it needs to fetch the latest data for the representation to be "now", so to speak.
a24sakma marked this conversation as resolved
a24sakma commented 2026-05-12 06:45:10 +00:00
Collaborator
Copy link

What works:

  • interfaces
  • endpoints
  • services
  • nginx

What needs to be changed:

  • check the above comments
  • update useParking url.
# What works: - interfaces - endpoints - services - nginx # What needs to be changed: - check the above comments - update useParking url.
Fixed the API_URL so the frontend doesn't break
Removed redundant variable
a24sakma commented 2026-05-12 08:04:51 +00:00
Collaborator
Copy link

Nice, it is ready to merge.

Nice, it is ready to merge.
a24julot merged commit 8e8e072df3 into team_1_week_5 2026-05-12 08:23:09 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
a24sakma
Labels
Clear labels   
_CRITICAL_

Only use this label for critical tasks that are project-scope,and must be addressed ASAP.

  
API

   
app

   
backEnd

   
Blocked-waiting-for-further-changes

   
bug

Something is not working

  
bug-only-on-server-for-mobile-not-webpage

   
Bug-Report-After-Merge

   
cleanup

Issues to cleanup the codebase (restructure folders, remove deprecated or smelly code)

  
close

Issue to close

  
design

   
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
feature request

   
frontEnd

   
further-changes-needed

   
future-problem-not-fixint-this-period

   
help wanted

Need some help

  
invalid

Something is wrong

  
last-week-issue-to-fix

   
library

   
low-priority

   
needs input

Issue needs input from product owner or customer

  
needs review

issue is in need of review

  
not-implemented.

   
project documentation

   
question

More information is needed

  
research

   
reviewed

This Issue has been reviewed

  
Script

   
security

use this for security-related issues

  
SQL

  
style

   
Team 1

Team 1 is responsible for this issue

  
Team 2

Team 2 is responsible for this issue

  
team leaders

   
test-creation

   
testing

   
topLevel

Reserved for top-level, project-wide issues.

  
unassigned

   
Under-review

   
wontfix

This won't be fixed

No labels
_CRITICAL_
API
app
backEnd
Blocked-waiting-for-further-changes
bug
bug-only-on-server-for-mobile-not-webpage
Bug-Report-After-Merge
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
further-changes-needed
future-problem-not-fixint-this-period
help wanted
invalid
last-week-issue-to-fix
library
low-priority
needs input
needs review
not-implemented.
project documentation
question
research
reviewed
Script
security
SQL
style
Team 1
Team 2
team leaders
test-creation
testing
topLevel
unassigned
Under-review
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Andras/BoundlessFlowCampus2K!892
No description provided.