Skip to content

Fix documentation parsing error #110

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 4, 2015

Conversation

vreemt
Copy link
Contributor

@vreemt vreemt commented Dec 4, 2015

the documentation incorrectly tries to use the success function when rendering the objectClass
this makes the display of the parameter more consistent

the documentation incorrectly tries to use the `success` function when rendering the `objectClass`
this makes the display of the parameter more consistent
@codecov-io
Copy link

Current coverage is 78.27%

Merging #110 into master will decrease coverage by -0.25% as of 78391e9

@@            master    #110   diff @@
======================================
  Files           37      37       
  Stmts         2822    2822       
  Branches       677     677       
  Methods          0       0       
======================================
- Hit           2216    2209     -7
- Partial        193     196     +3
- Missed         413     417     +4

Review entire Coverage Diff as of 78391e9

Powered by Codecov. Updated on successful CI builds.

@andrewimm
Copy link
Contributor

Good catch, appreciate the PR!

andrewimm added a commit that referenced this pull request Dec 4, 2015
Fix documentation parsing error
@andrewimm andrewimm merged commit b3356b2 into parse-community:master Dec 4, 2015
@vreemt
Copy link
Contributor Author

vreemt commented Dec 4, 2015

Is there any way I can test if it actually looks ok?
I figured making it match what's in other doc blocks (e.g. the ones for
Relations and Objects) would work, but no idea about testing it... feeling
like a bit of a noob (;
Thanks

2015-12-04 17:03 GMT+00:00 Andrew Imm [email protected]:

Good catch, appreciate the PR!


Reply to this email directly or view it on GitHub
#110 (comment)
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants