-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update entities due to API change #16
Comments
Hey, good catch. That's why we use contracts. According to this caution GET have been updated and do no longer return the @Dodje would you like to open a PR and fix the issue? I believe that deleting the P. S. It looks like that realworld-docs is in the process of updating right now. @geromegrignon Do we have a centralized place where we can view all upcoming updates? |
Yeah, I guess it will be possible for me to create a PR. But I believe there will be some other changes than deleting It still exists in single article dto, so we should separate Article and ArticleListItem. I'll check it again more carefully today later or tomorrow. |
Hello, indeed, as unused for the purpose of the UI I recently removed it from the public API responses as a solution to reduce the server traffic (as I had to move to a paid one). I'll double check the docs to ensure there is no mention left, I already removed it from the open API file. |
Currently there is no other plans to make changes due to the nature of the project: most implémentations are not maintained, making it hard to make breaking changes. It might change in the future but I'm focusing on a spin-off focused on Angular for a more complex (and so more RealWorld) application as a way to get a playground I'll be be able to update with ease unlike this one. I plan to add a proper documentation for anyone willing to create their own spin-off, like a one for React. |
@geromegrignon Sounds good, thank you for additional details. |
@yurisldk Hi again :) I went through the project today and found some other changes like "author.bio" -> optional for list item and nullable for single article. At first I thought that It might be a good idea to fully separate DTO's and logic between list item and single item on the frontend. But it seems that there gonna be really lots of changes like creating/separating features for favorite-feed-article/favorite-article or creating middle model for both at once, query mutations changes and so on. The simplest idea is to create ArticleListItemDto with optional What do you think? |
There is also missing |
let's do this. We also must pay attention to article entite`s and feature`s optimistic update logic. we can start with:
after that we have to take a look at features. Seems like we have to add additional mutation for article preview and cleanup article mutation optimistic update logic. At any case we have a good start point. |
The first part is completed. |
@geromegrignon I hope it's okay to ask you here since we've already begun the discussion. I went throw the docs and I found some issues with it:
|
@yurisldk I also have some questions to you if I may :) I've found some schema named |
I've pushed another commit 37d245c with favorite/unfavorite button changes. |
Seems like there were some changes in API. In particular endpoint of the list:
https://api.realworld.io/api/articles?limit=10
So there is the error while validation article schema: missing
body
prop..I've tried to find correct doc like swagger or whatever to ensure DTO change, but I wasn't able to find it to exact
api.realworld.io
. And those docs that I've found say thatbody
is expected to be.I guess there might be some bug in api, so we can wait and check. Or maybe it was done on purpose..
The text was updated successfully, but these errors were encountered: