Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sds-keyval
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • sds
  • sds-keyval
  • Issues
  • #4

Closed
Open
Created Nov 30, 2017 by Rob Latham@roblOwner

too many internal details exposed to user

The user API is mixed up with things that shouldn't be visible to the user. Right now the API is in sds-keyval.h, lines 294 to 310. The rest of this file is used internally. For instance the user is not supposed to see the actual implementation of kv_context_t, or the Mercury processing functions used for serialization. All this should be in a header that remains internal to sds-keyval, is used only when compiling it, and not installed. The user API should also be better documented.

Assignee
Assign to
Time tracking