Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / brikteknologier/seraph-resource issues and pull requests
#39 - Fixed deprecation error thrown by Express 4.x.x
Pull Request -
State: closed - Opened by bavellone about 9 years ago
#38 - I need suport in Express 4.X.X
Issue -
State: closed - Opened by Pompeu about 10 years ago
- 5 comments
#37 - Tests don't work with Express 4.0
Issue -
State: closed - Opened by MichaelJCole over 10 years ago
- 2 comments
#36 - Serving 'user' model collision with auth libraries.
Issue -
State: open - Opened by deestan almost 11 years ago
#35 - changed bodyParser to express.json && express.urlencoded to avoid depracation warnings
Pull Request -
State: closed - Opened by joaoafrmartins about 11 years ago
#34 - Support seraph's single-property support on single-property routes
Issue -
State: closed - Opened by jonpacker over 11 years ago
#33 - Caching is faulty in IE
Issue -
State: open - Opened by jonpacker over 11 years ago
- 2 comments
#32 - Composited push does not properly save the object as the correct model
Issue -
State: closed - Opened by jonpacker over 11 years ago
Labels: bug
#31 - Composition push route should return a single object not an array if only one object was saved
Issue -
State: closed - Opened by jonpacker over 11 years ago
#30 - Allow saving of multiple objects on push composition route
Issue -
State: closed - Opened by jonpacker over 11 years ago
- 1 comment
#29 - Strict content type application/json fails when firefox sends charset=UTF8 alongside
Issue -
State: closed - Opened by jonpacker over 11 years ago
#28 - Add route for deleting relationships
Issue -
State: open - Opened by jonpacker almost 12 years ago
#27 - DELETE type/:id should force-delete by default.
Issue -
State: closed - Opened by jonpacker almost 12 years ago
#26 - Gives 404 for nonexistent objects.
Pull Request -
State: closed - Opened by deestan almost 12 years ago
#25 - Reject non json
Pull Request -
State: closed - Opened by deestan almost 12 years ago
- 1 comment
#24 - test "Seraph Model HTTP Methods should handle deleting" failing on master.
Issue -
State: closed - Opened by deestan almost 12 years ago
- 2 comments
#23 - Use model to read rather than seraph
Issue -
State: closed - Opened by jonpacker almost 12 years ago
- 1 comment
#22 - Errors are being returned in the wrong order to express
Issue -
State: closed - Opened by jonpacker almost 12 years ago
- 1 comment
#21 - Support model composition
Issue -
State: closed - Opened by jonpacker almost 12 years ago
#20 - requesting a related nodes doesn't have content-type application/json
Issue -
State: closed - Opened by jonpacker almost 12 years ago
- 3 comments
#19 - Add api function for reading nodes of relationships
Issue -
State: closed - Opened by jonpacker almost 12 years ago
#18 - should use index to read models
Issue -
State: closed - Opened by jonpacker almost 12 years ago
- 1 comment
#17 - Validate that data was sent as an object before saving
Issue -
State: closed - Opened by jonpacker almost 12 years ago
- 2 comments
#16 - param throws error instead of passing to next
Issue -
State: closed - Opened by jonpacker over 12 years ago
- 1 comment
#15 - `res.end` called incorrectly
Issue -
State: closed - Opened by jonpacker over 12 years ago
#14 - make default routes more modular
Issue -
State: closed - Opened by jonpacker over 12 years ago
- 5 comments
Labels: on hold
#13 - document relationship functions
Issue -
State: closed - Opened by jonpacker over 12 years ago
#12 - update for controller 0.3
Issue -
State: closed - Opened by jonpacker over 12 years ago
#11 - document middleware groups
Issue -
State: closed - Opened by jonpacker over 12 years ago
#10 - update readme to reflect controller backing
Issue -
State: closed - Opened by jonpacker over 12 years ago
#9 - use express3's app.param
Issue -
State: closed - Opened by jonpacker over 12 years ago
#8 - should back onto controller
Issue -
State: closed - Opened by jonpacker over 12 years ago
#7 - make individual properties accessible if `model.fields` is defined
Issue -
State: closed - Opened by jonpacker over 12 years ago
#6 - Why? :)
Issue -
State: closed - Opened by deestan over 12 years ago
- 5 comments
#5 - make use of express.bodyParser() inferred
Issue -
State: closed - Opened by jonpacker over 12 years ago
- 1 comment
#4 - add routes that better expose graph-specific functionality
Issue -
State: closed - Opened by jonpacker over 12 years ago
#3 - add route specific middleware option
Issue -
State: closed - Opened by jonpacker over 12 years ago
#2 - Needs docs
Issue -
State: closed - Opened by jonpacker over 12 years ago
#1 - use proper status codes for errors
Issue -
State: closed - Opened by jonpacker over 12 years ago