Page:
Mock API Ceation Guidelines
Pages
API SMHI
API TimeEdit
Accessibility Testing
Api documentation
Bat/Ps
Branch Creation
C# Coding Convention
CSS Coding Convention
Coding Conventions
Creating new databases
Dapper
Documentation for service endpoints
Documentation of useTemperature and mock sensor
Energy endpoints
Environment
Evaluation react-grid-layout
Evaluation Localization
Evaluation Password hashing
Evaluation Testing framework
Evaluation of Logging Frameworks
Formatter
Frontend model
Generic Diagram for Sensor data flow
Home
How to- Creating Databases in Docker
Implementing different Styles
Implementing new Mockup sensors
Implementing new Views
Installation script documentation
Installation
Issues
JSON Coding Convention
Jest Testing
Layout endpoints
Linux
Localization
Login endpoints
Mac
Middleware model
Mock API Ceation Guidelines
Mockup models
Model Tools and Standards
Parking endpoints
React/JavaScript Coding Convention
React
Reviews
Room booking endpoints
SQL Coding Convention
Scheduled Database tasks
Scripting Coding Convention
Secrets and .env
Server Access
Server-Deployment
Service/API models
System models
System requirements
Temperature endpoints
Testing API with Bruno
Testing Architecture
Testing frontend for Mobile devices
Testing frontend with Playwright
Testing methodology
Västtrafik API
Webpage Design
Windows
pg_cron and scheduled database jobs
xUnit Testing
No results
2
Mock API Ceation Guidelines
Sakine Mazlomyar edited this page 2026-04-13 08:37:45 +00:00
The rules:
- Every micro service shall have a database. At the moment we use sensor database until the investigation about the database structure is done.
- Map Structure
- shall follow Object oriented (use of classes) check out the parking service structure
- Every micro service has unique functionalities such as electricity and sensor then some parts may not be similar
- Having a README: What to include:
- How it integrates from frontend and back
- How we reach the data and having proper comments
- In the pr having a label about testing
- How to build the project and make it run
- The decision and why
Communication
- At the moment the communication will happen through the middle-ware
- The update request is at the moment mockup until the investigation about how to handle it in the middleware and database.
When you create a new project, you need to first choose the correct template, then run the following command.
-"dotnet new <TEMPLATE> -n YOUR_PROJECT_NAME"
To list the available templates, use the command:
-"dotnet new list"
1. Setup
2. Standards
- Coding Conventions
- Issues
- Branch creation
- Reviews
- Implementation Standards
- [WIP] Creating new databases
- Localization
3. Models and Diagrams
4. Testing
5. Documentation
- Documentation for service endpoints
- API documentation
- Webpage Design
- Secrets and .env
- Evaluations
- Installation and Rebuild script documentation
6. Guides and How-to's
7. Micro Service Mockup Api
- Guidelines Mircro Service Mockup
- Documentation of useTemperature/useTemperatureTimeSeries mockup sensor