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

Unhide the stageview.open function for documentation #2065

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

sbtron
Copy link

@sbtron sbtron commented Nov 28, 2023

For more information about how to contribute to this repo, visit this page.

Description

Removing the hidden tag from the open function so that it can be documented correctly.

Main changes in the PR:

  1. remove hidden tag

Validation

Validation performed:

None. Doc update only

Unit Tests added:

None doc updates only

End-to-end tests added:

No

Additional Requirements

Change file added:

Ensure the change file meets the formatting requirements.

Yes

Related PRs:

N/A

Next/remaining steps:

More type doc updates could be made to explain other APIs better but we are still waiting for the functionality to roll out and will be making those as part of the rollouts.

@sbtron sbtron requested a review from a team as a code owner November 28, 2023 21:55
@@ -70,7 +70,6 @@ export namespace stageView {
}

/**
* @hidden
* Feature is under development
Copy link
Contributor

Choose a reason for hiding this comment

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

Should this ("Feature is under development") be removed? The @beta tag would imply that in the public documentation (and no other public beta features have this note)

@@ -0,0 +1,7 @@
{
"type": "none",
"comment": "removing hidden tag open function",
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
"comment": "removing hidden tag open function",
"comment": "Added documentation for `stageView.open`",

Changefiles should be written in past tense and should describe what effect the change would have that would matter to external developers (because these comments get added to the monthly patch notes)

Copy link
Contributor

Choose a reason for hiding this comment

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

Also, references to code (like stageView.open) should be surrounded by backticks (`) so that github formats them differently

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.

None yet

3 participants