Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Check the callbacks #117

Closed
1 task done
claucece opened this issue Jun 26, 2018 · 0 comments
Closed
1 task done

Check the callbacks #117

claucece opened this issue Jun 26, 2018 · 0 comments
Labels
API importance medium An issue that is medium level importance. It's good to have but not 100% necessary. interactive path
Projects
LibOTR-ng API

Comments

@claucece
Copy link
Member

claucece commented Jun 26, 2018 •
edited

Why

A Library should use callbacks correctly

Tasks

  • Check that all callbacks are defined correctly.
@claucece claucece added API importance medium An issue that is medium level importance. It's good to have but not 100% necessary. labels Jun 26, 2018
@claucece claucece added this to To do in LibOTR-ng API Jun 26, 2018
@claucece claucece mentioned this issue Jul 2, 2018
Closed
@claucece claucece moved this from To do to Q/A in LibOTR-ng API Jul 16, 2018
@claucece claucece moved this from Q/A to Done in LibOTR-ng API Aug 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
API importance medium An issue that is medium level importance. It's good to have but not 100% necessary. interactive path
Projects
No open projects
LibOTR-ng API
  
Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@claucece