Issue #108 [Card] Research/test display text card #182
No reviewers
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
6 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K!182
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "108-Research-test-display-text-card"
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?
Solution:
Made a view for viewing text elements.
Pair-programming with Nedzad (a24nedka)
Changes:
made file TextView.js under features/temperature
Notes:
The titel is set to Textview and the text element is lorem ipsum which needs to be changed when we have mockupdata.
Issue #108to Issue #108 [Card] Research/test display text cardTry to keep stuff in english for easier documentation.
Since this view also does not have anything to do with the temperature view, it should have its own map.
Feels like a kind of confusing issue, does not add a lot to the project from what I can tell? Do not know if it is worth merging or just keeping as documentation for now.
I think that the goal of this card was not to only display text, rather being able to add text to the card in a text field, like notes. I should have been more clear about that, sorry!
Review:
Code appears to execute as intended, nothing breaks. An editable text field appears under the temperature card in the app.
Code appears to follow to established coding standards for the most part. Naming conventions, spacing looks good.
However, lack of comments in the code makes it difficult to get a quick overview on what the different code sections actually "do", especially for those unfamiliar with the particulars of react, etc.
Recommendation: No obstacles exist to proceed with the merge, but do recommend adding comments to code.
/TempSensorMockup var data= new{sensor1} chaged to var data= new[]{sensor1,sensor2..} It used to give back a object with data of a single sensor now it returns an array with data from multiple sensors /readTempSensorMockup the read function used to expect an single object from tempSensorMockup but as its an array now its been changed to expect an array and a foreach loop have been intruduced to read and store the data from all sensors in the array /tempService i have included the sensorId in the class TempratureData, even if we stored sensorId,timestamp and temperature in the db we could only use the last two before in the View's/app it doesnt do anything now but its added to be able to make out witch sensor gives the reading.c3bfa738cdto73f4e7583cc3b3bfaf2ato73f4e7583ca4fa25fbfato73f4e7583cThe solution to the conflict is to take team_1's app.js and just commit it here. Tried some other solutions, didn't work... Just do that (after review), and the PR will be good to go
manually merged into temporary branch
Pull request closed