Add explicit classification docs #839
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pull Request Test Coverage Report for Build 2335
💛 - Coveralls |
sujaygarlanka
approved these changes
Sep 10, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We recently added explicit reference documentation to our API spec for handling Classifications. Classifications use metadata templates and instances, and therefore there's no seperate SDK methods for classifications.
In these documentation changes I've added a dedicated file to document how to use the metadata SDK methods to manipulate classifications. This doc, and the associated code samples can then be used in the developer documentation, mainly the API reference.
https://developer.box.com/reference/resources/classification/
We got a similar contribution merged to the Node SDK yesterday.
box/box-node-sdk#542