| Time |
S |
Nick |
Message |
| 00:06 |
|
|
digitalsanctum joined #rest |
| 01:08 |
|
|
digitalsanctum joined #rest |
| 02:08 |
|
|
fuzzyhorns joined #rest |
| 02:08 |
|
|
fuzzyhorns joined #rest |
| 02:09 |
|
|
digitalsanctum joined #rest |
| 03:02 |
|
|
baweaver joined #rest |
| 03:04 |
|
|
ralphschindler joined #rest |
| 03:10 |
|
|
digitalsanctum joined #rest |
| 04:47 |
|
|
lemur joined #rest |
| 04:58 |
|
|
digitalsanctum joined #rest |
| 05:12 |
|
|
jangid joined #rest |
| 06:46 |
|
|
digitalsanctum joined #rest |
| 07:31 |
|
|
wsiqueir joined #rest |
| 07:47 |
|
|
digitalsanctum joined #rest |
| 07:47 |
|
|
jangid joined #rest |
| 07:57 |
|
|
graste joined #rest |
| 08:00 |
|
|
interop_madness joined #rest |
| 08:02 |
|
|
jangid joined #rest |
| 08:09 |
|
|
jangid joined #rest |
| 08:22 |
|
|
rosstuck joined #rest |
| 08:44 |
|
|
jangid joined #rest |
| 08:58 |
|
|
mgomezch joined #rest |
| 09:35 |
|
|
digitalsanctum joined #rest |
| 11:06 |
|
|
jangid joined #rest |
| 11:15 |
|
|
mezod joined #rest |
| 11:18 |
|
|
chthon joined #rest |
| 11:23 |
|
|
digitalsanctum joined #rest |
| 11:51 |
|
|
eschmidbauer joined #rest |
| 11:54 |
|
|
eschmidbauer left #rest |
| 11:54 |
|
|
digitalsanctum joined #rest |
| 12:11 |
|
|
digitals_ joined #rest |
| 14:54 |
|
|
fuzzy_horns joined #rest |
| 14:56 |
|
|
AllTuna joined #rest |
| 14:57 |
|
AllTuna |
Heya |
| 15:28 |
|
AllTuna |
I'm trying to wrap my head around naming conventions for my REST API implementation |
| 15:28 |
|
AllTuna |
If I use something like /venues/2917 |
| 15:28 |
|
AllTuna |
and each venue has a menu and menu items |
| 15:29 |
|
AllTuna |
is it bad practice to use /venues/2917/menu |
| 15:29 |
|
asdf` |
AllTuna, nah, it's ok, why would it be bad? |
| 15:29 |
|
AllTuna |
I just feel like menu isn't plural |
| 15:29 |
|
asdf` |
AllTuna, REST doesn't care much about naming really, but more that the urls should be discoverable rather than hardcoded into the client |
| 15:30 |
|
AllTuna |
so even though I'm using venues as plural and menu as singular, that is alright? |
| 15:31 |
|
asdf` |
sure; i don't think anyone will care either way |
| 15:31 |
|
sfisque |
are there other components that menu could be grouped with? like a collection of UI components and menu is "one of the bunch"? |
| 15:32 |
|
AllTuna |
Hmm, you mean in case I should be using menu as a child of another noun> |
| 15:33 |
|
sfisque |
something like …./uiComponents -> { menu : { some attributes }, selector : {some attributes }, etc…. } |
| 15:33 |
|
sfisque |
and you could walk down that if need be |
| 15:33 |
|
sfisque |
if you really don't like having a singular node in your URI |
| 15:34 |
|
AllTuna |
Oh I see |
| 15:34 |
|
AllTuna |
Not that I can think of |
| 15:34 |
|
AllTuna |
I'm currently developing the MVP of my platform, so I don't think theres much more than the menu at this stafe |
| 15:34 |
|
AllTuna |
stage* |
| 15:34 |
|
sfisque |
i guess does it make sense to have menu be a "top level" object vs. just an attribute of the node |
| 15:34 |
|
fumanchu_ |
but there's no reason to avoid singular nouns. It's quite common to have a 1:1 or many:1 relationship between different resources |
| 15:34 |
|
sfisque |
^^^ truth |
| 15:35 |
|
AllTuna |
Alright, I feel better about that then |
| 15:37 |
|
AllTuna |
Could someone give me an example of a request to th API if someone were to buy something from a store |
| 15:37 |
|
AllTuna |
for example a book from the amazon store? |
| 15:38 |
|
AllTuna |
It wouldn't be linked to the request on that book, but rather a request on something like /order?id=234 |
| 15:38 |
|
AllTuna |
Right? |
| 16:09 |
|
|
mezod joined #rest |
| 18:03 |
|
|
jangid joined #rest |
| 18:12 |
|
|
graste joined #rest |
| 18:39 |
|
|
digitalsanctum joined #rest |
| 20:16 |
|
|
Coldblackice joined #rest |
| 20:57 |
|
|
_ollie joined #rest |
| 21:02 |
|
|
foist joined #rest |
| 21:59 |
|
|
fuzzyhorns joined #rest |
| 22:06 |
|
|
talios joined #rest |
| 23:49 |
|
|
mezod joined #rest |
