This repository has been archived by the owner on Apr 5, 2022. It is now read-only.
Create company "Shares" #62
Open
Conversation
This file contains 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
|
Can this be flushed out and merged? Would very much like this capability |
|
@BobbyJohansen given the lack of activity on this project and the age of this PR, I wouldn't hold my breath. 😞 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Adds functionality to create "Shares" for companies. See https://developer.linkedin.com/creating-company-shares. It also includes the ability to target company Shares (see https://developer.linkedin.com/documents/targeting-company-shares). This last part, however, is broken on the LinkedIn side when exchanging JSON payloads (see https://developer.linkedin.com/forum/targeting-example-using-multiple-targeting-parameters-and-json) so I had to revert to using XML instead. This introduces the use of XStream and adds extra logic to error handlers and interceptors. This can be "sanitized" once LinkedIn fixes their API.