Skip to content
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

Opt in documentation #28

Open
wants to merge 14 commits into
base: master
Choose a base branch
from
Open

Opt in documentation #28

wants to merge 14 commits into from

Conversation

trevorflahardy
Copy link
Collaborator

@trevorflahardy trevorflahardy commented Oct 12, 2024

Summary

This PR updates documentation to include information regarding the newly added ResponseFlags class in the library.

  • Updates the migration guide to include the response_flags parameter in the client.
  • Creates a Response Flags section in the documentation describing what response flags are and how to use them.
  • Creates a .. opt-in sphinx directive that marks an attribute as needing to be marked-in.
  • Updates all relevant attributes with said sphinx directive.
image image

Checklist

  • If code changes were made then they have been tested.
    • I have updated the documentation to reflect the changes.
  • This PR fixes an issue.
  • This PR adds something new (e.g. new method or parameters).
  • This PR is a breaking change (e.g. methods or parameters removed/renamed)
  • This PR is not a code change (e.g. documentation, README, ...)

@trevorflahardy trevorflahardy added the documentation Improvements or additions to documentation label Oct 12, 2024
@trevorflahardy trevorflahardy self-assigned this Oct 12, 2024
@trevorflahardy trevorflahardy linked an issue Oct 12, 2024 that may be closed by this pull request
@trevorflahardy trevorflahardy marked this pull request as ready for review October 12, 2024 17:45
Copy link
Member

@Luc1412 Luc1412 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, but directive is applied to attributes that are not part of the opt-in.

Comment on lines 440 to +443
display_asset_path: Optional[:class:`str`]
The display asset path of this entry.

.. opt-in:: INCLUDE_PATHS
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This field isn't affected by opt-in params.

Comment on lines 112 to +119
gameplay_tags: List[:class:`str`]
The gameplay tags for the playlist.

.. opt-in:: INCLUDE_GAMEPLAY_TAGS
path: :class:`str`
The path of the playlist.

.. opt-in:: INCLUDE_PATHS
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both fields are not affected by opt-in params.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should emphasize the user to only use the required opt-in parameters they actually need. And how the user benefits from it. (e.g. perfomance, bandwith)

Comment on lines 248 to +251
display_asset_path: Optional[:class:`str`]
The display asset path of the cosmetic, if available.

.. opt-in:: INCLUDE_PATHS
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This attribute seems to not present anymore. I need to check back with Officer about it's status.

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

Successfully merging this pull request may close these issues.

Add info regarding opt-in attributes
2 participants