-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GET Bot Data api #452
GET Bot Data api #452
Conversation
done(err); | ||
} | ||
|
||
expect(res.body.length).to.equal(ONE); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you intend to check the contents here as well? Or that implementation is still pending?
api/v1/controllers/botData.js
Outdated
* @param {Function} next - The next middleware function in the stack | ||
*/ | ||
findRoomBotBotData(req, res, next) { | ||
doFind(req, res, next, helper); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am confused. Do you intend to update the doFind logic for roomIds and botIds or is it already in place?
will not review until tests passing |
* master: DELETE BotData API (#457) # Conflicts: # api/v1/controllers/botData.js # api/v1/helpers/nouns/botData.js
@tausifmuzaffar Some conflicts to resolve here. |
* master: PATCH BotData (#454) # Conflicts: # api/v1/controllers/botData.js # api/v1/helpers/nouns/botData.js # api/v1/swagger.yaml
* master: GET Bot Data api (#452) # Conflicts: # api/v1/controllers/botData.js # api/v1/helpers/nouns/botData.js # api/v1/swagger.yaml
/botData
/botData/key
/rooms/key/data
/rooms/key/bot/key/data