Some API endpoints for articles
#245
Sammanfogat
elegaanz
sammanfogade 4 incheckningar från rest-api
in i master
6 år sedan
Granskare
Begär granskning
Inga granskare
Etiketter
Rensa etiketter
Related to the REST API
Code running on the server
Stuff related to Federation
Related to the front-end
Translations, and related code
More about project management or code than the project itself
The building, or installation process of Plume
Something isn't working
We need to talk
New feature or request
This is a new feature
Compatibility with different browsers, readers and OS
Related to an external package that Plume uses
UI/UX related issues and PRs
Good for newcomers
Extra attention is needed
Issues affecting only mobile UX
How elements're rendered out for the end user
Something else needs to be fixed first
This issue or pull request already exists
This PR is not complete yet
Issues concern a limited number of instances
This doesn't seem right
Need to be discussed by the community (on Loomio)
This PR is ready to be reviewed
Proposed ideas worth considering
This is issue has been created after a vote on Loomio
This will not be worked on
Tillämpa etiketter
A: API
Related to the REST API
A: Backend
Code running on the server
A: Federation
Stuff related to Federation
A: Front-End
Related to the front-end
A: I18N
Translations, and related code
A: Meta
More about project management or code than the project itself
A: Security
Build
The building, or installation process of Plume
C: Bug
Something isn't working
C: Discussion
We need to talk
C: Enhancement
New feature or request
C: Feature
This is a new feature
Compatibility
Compatibility with different browsers, readers and OS
Dependency
Related to an external package that Plume uses
Design
UI/UX related issues and PRs
Documentation
Good first issue
Good for newcomers
Help welcome
Extra attention is needed
Mobile
Issues affecting only mobile UX
Rendering
How elements're rendered out for the end user
S: Blocked
Something else needs to be fixed first
S: Duplicate
This issue or pull request already exists
S: Incomplete
This PR is not complete yet
S: Instance specific
Issues concern a limited number of instances
S: Invalid
This doesn't seem right
S: Needs Voting/Discussion
Need to be discussed by the community (on Loomio)
S: Ready for review
This PR is ready to be reviewed
Suggestion
Proposed ideas worth considering
S: Voted on Loomio
This is issue has been created after a vote on Loomio
S: Wontfix
This will not be worked on
Ingen Etikett
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
Milsten
Ange milstolpe
Rensa milstenar
Inga objekt
Ingen Milsten
Tilldelade
Tilldela användare
Rensa tilldelade
Ingen tilldelad
2 Deltagare
Notiser
Förfallodatum
Förfallodatumet är ogiltigt eller utanför gränserna. Använd formatet 'åååå-mm-dd'.
Inget förfallodatum satt.
Beroenden
No dependencies set.
Reference: Plume/Plume#245
Referens i nytt ärende
Det finns inget innehåll än.
Ta bort branch 'rest-api'
Borttagning utav en branch är permanent. Detta KAN INTE ångras. Vill du fortsätta?
Nej
Ja
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
.236cf14406
.Step 1:
From your project repository, check out a new branch and test the changes.Step 2:
Merge the changes and update on Forgejo.