You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While writing tests, a few "magic numbers" popped up. Turns out no all @getdnsapi/getdns API constants have been implemented in getdns-node/src/GNConstants.cpp.
Might more be missing?
How can changes in the @getdnsapi/getdns API -- past or future -- be detected on the code level, so that the "diff" can be implemented in getdns-node?
The closest thing that comes to mind is to diff getdns/src/getdns/getdns.h.in between releases. What the changes actually mean would then be lookup up in the API documentation. Is that enough?
The text was updated successfully, but these errors were encountered:
joelpurra
added a commit
to joelpurra/getdns-node
that referenced
this issue
Apr 2, 2017
- Constants are pulled from `getdns/src/getdns/getdns.h.in` and `getdns/src/getdns/getdns_extra.h.in`.
- Text strings have not been included yet.
- Version strings etcetera have been skipped for now.
- The rest has been added blindly.
- This should reduce magic number usage and facilitate return code checks.
- Future versions might (reintroduce) javascript level constant exports using ES6 modules.
This relates to getdnsapi#18, but is not a complete solution. Functions, and possibly other things, still need to be checked.
While writing tests, a few "magic numbers" popped up. Turns out no all @getdnsapi/getdns API constants have been implemented in
getdns-node/src/GNConstants.cpp
.The closest thing that comes to mind is to diff
getdns/src/getdns/getdns.h.in
between releases. What the changes actually mean would then be lookup up in the API documentation. Is that enough?The text was updated successfully, but these errors were encountered: