API vs Front (which needs to adapt?)
up vote
0
down vote
favorite
i have a general question about API and Front. I'm making a website with an API and ReactJS. For example, i have a ressource /product/detail
which return name, price and category. If my react doesnt need the category, should it just ignore category (and have useless infos in request) or is it to the API to adapt and return only name and price.
It's for largest things, just wanted to know what's the best thing, why and what you think about it. Is a "good" practice or it just depends ?
Thx. (sorry bad english =)
api frontend
asked Nov 19 at 13:25
Tralgar
1
New contributor
Tralgar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
i have a general question about API and Front. I'm making a website with an API and ReactJS. For example, i have a ressource /product/detail
which return name, price and category. If my react doesnt need the category, should it just ignore category (and have useless infos in request) or is it to the API to adapt and return only name and price.
It's for largest things, just wanted to know what's the best thing, why and what you think about it. Is a "good" practice or it just depends ?
Thx. (sorry bad english =)
api frontend
asked Nov 19 at 13:25
Tralgar
1
New contributor
Tralgar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Might another frontend need that information? If so, keep it in the API. If not, remove it.
– Michael
Nov 19 at 13:27
Ok thx, my API is dedicated to one and only front, so i should remove it... But my vision is not really clear of what is the best in a more complexe situation
– Tralgar
Nov 20 at 14:32
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
i have a general question about API and Front. I'm making a website with an API and ReactJS. For example, i have a ressource /product/detail
which return name, price and category. If my react doesnt need the category, should it just ignore category (and have useless infos in request) or is it to the API to adapt and return only name and price.
It's for largest things, just wanted to know what's the best thing, why and what you think about it. Is a "good" practice or it just depends ?
Thx. (sorry bad english =)
api frontend
asked Nov 19 at 13:25
Tralgar
1
New contributor
Tralgar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
i have a general question about API and Front. I'm making a website with an API and ReactJS. For example, i have a ressource /product/detail
which return name, price and category. If my react doesnt need the category, should it just ignore category (and have useless infos in request) or is it to the API to adapt and return only name and price.
It's for largest things, just wanted to know what's the best thing, why and what you think about it. Is a "good" practice or it just depends ?
Thx. (sorry bad english =)
api frontend
api frontend
asked Nov 19 at 13:25
Tralgar
1
New contributor
Tralgar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 19 at 13:25
Tralgar
1
New contributor
Tralgar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 19 at 13:25
Tralgar
1
New contributor
Tralgar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 19 at 13:25
Tralgar
1
asked Nov 19 at 13:25
Tralgar
1
1
New contributor
Tralgar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Tralgar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Tralgar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Might another frontend need that information? If so, keep it in the API. If not, remove it.
– Michael
Nov 19 at 13:27
Ok thx, my API is dedicated to one and only front, so i should remove it... But my vision is not really clear of what is the best in a more complexe situation
– Tralgar
Nov 20 at 14:32
add a comment |
Might another frontend need that information? If so, keep it in the API. If not, remove it.
– Michael
Nov 19 at 13:27
Ok thx, my API is dedicated to one and only front, so i should remove it... But my vision is not really clear of what is the best in a more complexe situation
– Tralgar
Nov 20 at 14:32
Might another frontend need that information? If so, keep it in the API. If not, remove it.
– Michael
Nov 19 at 13:27
Might another frontend need that information? If so, keep it in the API. If not, remove it.
– Michael
Nov 19 at 13:27
Ok thx, my API is dedicated to one and only front, so i should remove it... But my vision is not really clear of what is the best in a more complexe situation
– Tralgar
Nov 20 at 14:32
Ok thx, my API is dedicated to one and only front, so i should remove it... But my vision is not really clear of what is the best in a more complexe situation
– Tralgar
Nov 20 at 14:32
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Tralgar is a new contributor. Be nice, and check out our Code of Conduct.
Tralgar is a new contributor. Be nice, and check out our Code of Conduct.
Tralgar is a new contributor. Be nice, and check out our Code of Conduct.
Tralgar is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53375628%2fapi-vs-front-which-needs-to-adapt%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Might another frontend need that information? If so, keep it in the API. If not, remove it.
– Michael
Nov 19 at 13:27
Ok thx, my API is dedicated to one and only front, so i should remove it... But my vision is not really clear of what is the best in a more complexe situation
– Tralgar
Nov 20 at 14:32