cybertk / cybertk/abao

Features desired

Open
#2 18 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
CoffeeScript
Stars
352
Forks
57
PR merge metrics
No merged PRs in 30d

Description

- [x] `test.request.body` should be object when `Content-Type` is `application/json`
- [ ] Should not display pending test if invoke abao with `--hook-only`
- [x] Should give a warning if `Content-Type` is not `application/json`
- [ ] Should give a warning if hook is ignored
- [ ] Let hook's `done` param optional
- [ ] Validate fail if an array field contains no elements
- [ ] [gulp-abao](http://github.com/cybertk/gulp-abao)
- [ ] [grunt-abao](http://github.com/cybertk/grant-abao)
- [ ] [abao-example](http://github.com/cybertk/abao-example)

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue is a broad checklist covering test.request.body, --hook-only behavior, hook warnings and callbacks, array validation, and gulp-abao, grunt-abao, and abao-example integrations. Start by locating the entry points for these features and reviewing the existing tests; done would require agreed scope and completion of the selected unchecked items.

Written by the indexing model from the issue text.

Assessment

Tech stack
coffeescript
Domain
api, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.