Some API endpoints for articles #245
Brak recenzentów
Etykiety
Brak etykiet
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
Brak kamienia milowego
Brak projektu
Brak przypisanych
Uczestnicy 2
Powiadomienia
Termin realizacji
Brak ustawionego terminu realizacji.
Zależności
Brak ustawionych zależności.
Odniesienie: Plume/Plume#245
Ładowanie…
Dodaj tabelę
Odniesienie w nowym zgłoszeniu
Opis zgłoszenia jest pusty.
Usuń gałąź "rest-api"
Usunięcie gałęzi jest permanentne. Mimo, że usunięta gałąź może istnieć przez krótki czas zanim zostanie rzeczywiście usunięta, ta operacja NIE MOŻE zostać cofnięta w większości przypadków. Kontynuować?
canapi::Provider
forPost
(onlyget
andlist
actually)/api/v1/posts/<id>
and/api/v1/posts
)It is a first step for #5
👀
@ -5,6 +5,7 @@ version = "0.2.0"
[dependencies]
activitypub = "0.1.3"
atom_syndication = "0.6"
canapi = "0.1"
exciting Version number
@ -0,0 +1,45 @@
openapi: "3.0"
is this autogenerated?
@ -0,0 +13,4 @@
}
}
};
}
sometimes i dream of lisp indentation style in Javascript. soon, I'll start dreaming of lisp indentation style in rust
@ -58,0 +93,4 @@
}
fn create(_conn: &PgConnection, _query: PostEndpoint) -> Result<PostEndpoint, Error> {
unimplemented!()
what's the point of these queries and the override of the query variable?
aahh, you're fetching different parts of the same article, and stuffing them into different boxes of the query variable!
why does this file keep changing with every new build?
such as?
@ -0,0 +1,45 @@
openapi: "3.0"
not yet, but it may be possible thanks to canapi…
it is updated every time you run Plume. However, extracting i18n related task to an external tool may be better… 🤔
For instance, if you
GET /api/v1/posts?title=Hello%20world
, only posts with theHello world
title should be shown (title
is not the best example, butauthor_id
could be interesting for instance)@ -58,0 +93,4 @@
}
fn create(_conn: &PgConnection, _query: PostEndpoint) -> Result<PostEndpoint, Error> {
unimplemented!()
actually, the
PostEndpoint
type is here to represent both the client's query and the result sent by the API.filter
is what is requested by the client, so if any filter have been specified I update the SQLquery
to only return the requested posts.@ -58,0 +93,4 @@
}
fn create(_conn: &PgConnection, _query: PostEndpoint) -> Result<PostEndpoint, Error> {
unimplemented!()
not sure if I'm clear, tell me if not 😁
i just realized how easy CLI mappings would be to implement, once the API is in place.
So is this (at least partially) blocked by #149, or not related?
No, actually we just need to get the raw query params, and deserialize them to
PostEndpoint
with something likeserde_qs
.