Attribute field naming #19
Open
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
added 6 commits
April 14, 2015 08:24
This was needed to implement initialization of the "environment" field Now it is possible to have differences between propertynames and form-keys
packages.config: Restsharp is now 104.1
JiraClient: - Avoided long lines - Removed .ToArray() after GetProperties() - Placed one line if out of block
schoetbi
force-pushed
the
AttributeFieldNaming
branch
from
3b8428a to
17fe15d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Implemented possiblity to mark the properties of the TIssueFields class with attributes to have different names for the post message variables
Respected quexys comments in PullRequest #18