| Time |
S |
Nick |
Message |
| 00:46 |
|
|
fred-fri joined #rest |
| 00:59 |
|
|
FreezingDroid joined #rest |
| 01:02 |
|
|
fuzzyhorns joined #rest |
| 02:09 |
|
|
fumanchu joined #rest |
| 02:30 |
|
|
fuzzyhorns joined #rest |
| 02:51 |
|
|
fuzzy_horns joined #rest |
| 02:52 |
|
|
fuzzyhorns joined #rest |
| 04:39 |
|
|
fuzzyhorns joined #rest |
| 06:28 |
|
|
fuzzyhorns joined #rest |
| 07:42 |
|
|
_ollie joined #rest |
| 07:49 |
|
|
interop_madness joined #rest |
| 07:51 |
|
|
fsvehla joined #rest |
| 08:17 |
|
|
fuzzyhorns joined #rest |
| 09:05 |
|
|
quimrstorres joined #rest |
| 09:18 |
|
|
quimrstorres joined #rest |
| 09:51 |
|
|
Left_Turn joined #rest |
| 10:06 |
|
|
fuzzyhorns joined #rest |
| 10:23 |
|
|
quimrstorres joined #rest |
| 11:32 |
|
|
quimrstorres joined #rest |
| 11:54 |
|
|
fuzzyhorns joined #rest |
| 12:22 |
|
|
_ollie1 joined #rest |
| 12:38 |
|
|
_ollie joined #rest |
| 13:03 |
|
|
quimrstorres joined #rest |
| 13:10 |
|
|
fuzzyhorns joined #rest |
| 13:44 |
|
|
quimrsto_ joined #rest |
| 13:45 |
|
|
fuzzyhorns joined #rest |
| 13:59 |
|
|
quimrstorres joined #rest |
| 14:05 |
|
|
saml joined #rest |
| 15:22 |
|
|
baweaver joined #rest |
| 15:42 |
|
|
Fat-Zer_ joined #rest |
| 15:43 |
|
|
quimrsto_ joined #rest |
| 15:43 |
|
|
Fat-Zer_ left #rest |
| 15:43 |
|
|
Fat-Zer_ joined #rest |
| 16:49 |
|
|
Left_Turn joined #rest |
| 17:19 |
|
|
quimrstorres joined #rest |
| 18:01 |
|
|
quimrsto_ joined #rest |
| 18:24 |
|
|
Char_ joined #rest |
| 18:25 |
|
Char_ |
hey I have a questions, on my frontend I have a date field that can be changed and next to it is a checkbox, which shows whether it is disabled or not, how should I handle it in my rest request, should I send both, the boolean value and date value to the backend and store in database, or if the date field is disabled, I should store the value as null, so I do not have to make 2 fields |
| 18:27 |
|
whartung |
are you saying that the date is optional? |
| 18:27 |
|
sfisque1 |
i think he's trying to drive the UI from the server side |
| 18:28 |
|
Char_ |
well the date is optional, since if its disabled, it should not be used in backend |
| 18:28 |
|
sfisque1 |
aka, the server indicates the field is RO or RW and the UI adjusts |
| 18:28 |
|
whartung |
I mean, if it's optional, then optionally don't send it... |
| 18:29 |
|
sfisque |
or simply allow it to be sent and just discard if it does not make sense |
| 18:29 |
|
sfisque |
rest endponts are supposed to be ux agnostic |
| 18:29 |
|
Char_ |
im just thinking if I should store the date and the boolean value in database, or just the date value and the boolean in the same variable, meaning that it can be also nullable |
| 18:30 |
|
Char_ |
then if checkbox is false, then the date will be null in db |
| 18:30 |
|
whartung |
Is it up to the client as to whether to send the date? I mean, when the date optional, and who determines that? |
| 18:31 |
|
sfisque |
well, either way you're storing null, so why would you need the boolean? |
| 18:32 |
|
Char_ |
well its a update form, soo if the date box is disabled. the date will be still stored in DB and displayed to user, meaning it shows which value he last used there, but its just disabled |
| 18:33 |
|
sfisque |
aye, but then you're coupling your rest endpoint to the ux |
| 18:33 |
|
sfisque |
which is fine, if that's what you want |
| 18:34 |
|
Char_ |
sfisque what do you mena under coupling my rest endpoint to the ux? |
| 18:36 |
|
sfisque |
it seems the point of this boolean value is to drive the UX, which means part of the data you are sending/receiving has nothing to do with the actual data but how the client is supposed to manage the user experience |
| 18:41 |
|
Char_ |
sfisque yes that might be the case |
| 18:42 |
|
Char_ |
sfisque you seem to know alot about REST design, I would like to sometimes talk about design and maybe you can help me out |
| 18:42 |
|
Char_ |
can I get your skype? |
| 18:43 |
|
sfisque |
i know "enough to be dangerous". there are better qualified peeps in channel :P |
| 18:43 |
|
sfisque |
and i don't use skype anymore, ever since M$ fudged it all up |
| 18:43 |
|
Char_ |
oh alright |
| 18:44 |
|
Char_ |
I still use it, seems to be fine |
| 18:44 |
|
fumanchu |
the main data design (and therefore REST API design) question here is whether you want to allow users to retain a real date value even when the box is not checked. That is, if they disable the date and then decide to re-enable it, do they have to re-enter the valid date or is it sitting there waiting for them? |
| 18:45 |
|
fumanchu |
if they have to re-enter it then null is fine. if not, you need two fields |
| 18:46 |
|
whartung |
may as well keep your design questions here Char_, that way others can learn and participate |
| 18:46 |
|
fumanchu |
(unless you're keeping track of changes and can go scan the history to see what the date used to be some other way) |
| 18:46 |
|
Char_ |
okay, thanks guys alot |
| 19:07 |
|
|
quimrstorres joined #rest |
| 19:18 |
|
|
Coldblackice joined #rest |
| 19:22 |
|
|
quimrstorres joined #rest |
| 20:08 |
|
|
_ollie joined #rest |
| 20:52 |
|
|
daxim joined #rest |
| 20:57 |
|
|
quimrstorres joined #rest |
| 21:04 |
|
|
fuzzyhorns joined #rest |
| 21:08 |
|
|
warehouse13 joined #rest |
| 21:13 |
|
|
_ollie joined #rest |
| 21:34 |
|
|
pgicxplzs joined #rest |
| 21:45 |
|
|
warehouse13 joined #rest |
| 22:27 |
|
|
quimrstorres joined #rest |
| 23:30 |
|
|
quimrstorres joined #rest |
