You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, when printing a "Booking" object, we get back a result of an object type. Even though that doesn't necessarily affect the way the application is running at the moment, it could cause problems in the future when debugging.
To identify the issue, follow the steps below.
Good observation - not sure we can justify it being high priority (the booking objects are only designed to be accessed/displayed via the front-end) but I can't see it causing any harm to make the suggested change, we'll have a think about doing this in a later sprint
Version
v2
Impact
High
Suggested Priority
High
Description
At the moment, when printing a "Booking" object, we get back a result of an object type. Even though that doesn't necessarily affect the way the application is running at the moment, it could cause problems in the future when debugging.
To identify the issue, follow the steps below.
In the CLI run:
You will get a result similar to this:
<lib.booking.Booking object at 0x1047a61e0>
To fix this I suggest adding a repl method in the booking.py:
If afer adding the repl method we repeat the steps in the REPL, we should now be getting the result below:
Booking(135, "2024-06-05 21:21", 1, 2, 3)
The text was updated successfully, but these errors were encountered: