Changed :type: to :class: in dropbox.file_properties

[BastianZim]

Changed :type: to :class:, which gets correctly rendered by readthedocs.

Before:

After:

Checklist

General Contributing

• Have you read the Code of Conduct and signed the CLA?

Is This a Code Change?

• Non-code related change (markdown/git settings etc)
• SDK Code Change
• Example/Test Code Change

Validation

• Does tox pass?
• Do the tests pass?

[codecov]

Codecov Report

Merging #252 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #252   +/-   ##
=======================================
  Coverage   46.98%   46.98%           
=======================================
  Files          32       32           
  Lines       77334    77334           
  Branches     6370     6370           
=======================================
  Hits        36332    36332           
  Misses      40951    40951           
  Partials       51       51           

Flag	Coverage Δ
#unit	46.98% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
dropbox/file_properties.py	48.98% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6105d87...c586d21. Read the comment docs.

[greg-db]

Thanks for submitting this.

@rogebrd can take a look, but this may need to actually be changed in the spec itself, or maybe this is something for the generator to handle.

[BastianZim]

Pleasure!

No worries, I just wanted to open it so that it’s documented but feel free to close it if the cause is somewhere else.

[rogebrd]

Sorry for the delay on the response. This will require an internal change to the spec itself so I have opened a diff on our internal repo. Once that is approved, this change will come in the next spec update. I will leave this open for tracking until then!

[BastianZim]

Ok perfect, no worries thanks for the update!

[rogebrd]

Hey, I put out a fix to Stone to fix this issue. We have an upcoming task to upgrade stone past 1.X which this PR will be blocked on that completing. Hopefully this isn't causing any immediate issues for you!

[BastianZim]

Hi, thanks for the update. No, no problems here, I'll close the PR then.