Create template for how mockup Sensors are made #636
Labels
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
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#636
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We need sort of a template how mockup sensors should be made. This needs diagrams, explanations and a Wiki page.
Findings and discussions can be posted here, both to discuss and also get activity.
Do not forget to link the wiki page in this issue in order to back-track back to this issue.
The diagram for tempService can be found here, in issue #590.
The diagram shows folder and file structure as well as data flow, so it's useful as a guide/reference for this issue to understand the flow of a sensor service.
Generic diagrams for mockup sensors and mockup api now have a wiki page here.
https://git.webug.se/Andras/BoundlessFlowCampus2K/wiki/Mockup-models
This has been reviewed. I close this issue.