The publish sequence in Travis CI
- Support
IncludeQuery
,FieldsQuery
,SortQuery
,PageQuery
andFilterQuery
PageQuery
:- Support
CursorBased
,PageBased
andOffsetBased
- The type of
PageQuery
are auto-recognized, checkingOffsetBased
first, thenPageBased
, thenCursorBased
- Support
FilterQuery
:- Support
Rsql
- Support
- Pretty and extendable Error System, most of the StatusCode in Error System are based on Specification
- See project panel for the detail of Fetching Operation
- Publish error: all dependencies must have a version specified when publishing.
The most important and bothering thing is that attributes
cannot be sorted
rabbithole::model::query::Query
model forMy final goal to this project
inREADME.md
- Basic actix_web support (see
examples/mock_gen.rs
for more details) - An actix-web based web server
- A example project showing the basic features
- A lot more tests
- A Rule System ready for the different operations when the jsonapi version changes
- Mark the
impl<T: Entity> Entity for Vec<T>
asunstable-vec-to-document
- Change
to_document
to longerto_document_automatically
to encourage users using their own version, rather than the auto version for better performance - Split
Entity
intoEntity
andSingleEntity
, where:SingleEntity
has all of the params likety()
,id()
where only the single entity will haveEntity
defines the more general functions likeincluded
andto_document_automatically
, whereVec<T>
or[T]
will also have. But of course, they have no the param likeid
- Error System now is much better now
- JSON:API Data Structure
- A user-friendly macro system and Entity System (
rabbithole::entity::Entity
) - Basic tests
- TravisCI support
- README/CHANGELOG docs