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

Forms navigation XML docs #2475

Closed
wants to merge 7 commits into from

Conversation

Adam--
Copy link
Contributor

@Adam-- Adam-- commented Jun 8, 2021

Description of Change

Addresses part of #1978, Add Missing XML Docs, adding documentation for all public members and classes within Prism.Forms Navigation.

Bugs Fixed

None

API Changes

None

Added:

None

Changed:

None

Behavioral Changes

None

PR Checklist

  • Has tests (if omitted, state reason in description)
  • Rebased on top of master at time of PR
  • Changes adhere to coding standard

@Adam-- Adam-- requested a review from dansiegel as a code owner June 8, 2021 16:12
@Adam-- Adam-- changed the title Forms navigation docs Forms navigation XML docs Jun 8, 2021
@Adam--
Copy link
Contributor Author

Adam-- commented Jun 11, 2021

@dansiegel I don't think these changes caused the end to end Uno UITests to fail. Does this need to be fixed before merging?

@dansiegel
Copy link
Member

No your changes wouldn't have caused anything to fail... I'll review this when I get a chance

public interface INavigationResult
{
/// <summary>
/// <see langword="true"/> if the navigation was successful, <see langword="false"/> otherwise.
Copy link
Member

Choose a reason for hiding this comment

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

May be false with a null exception if CanNavigate returned false

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Not sure I'm following your correction here. If CanNavigate returns false, then that is not a successful navigation so the summary for Success still sounds correct.

The summary for INavigationResult isn't correct however and I think it'd be best to update it to be a bit more generic, something like "Provides navigation results indicating if the navigation was successful and any exceptions caught".

What do you think?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I went ahead and made those changes. In the descriptions of INavigationResult it now doesn't imply there is an exception when success is false.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@dansiegel Are you okay with these changes, can we get this PR merged?

The wording before suggested that if the navigation request was
unsuccessful there would be an exception captured; however, this is not
the case when navigation is attempted and CanNavigate is false. In this
case, Success would be false and Exception would be null.

The wording now does not make that suggestion.
@Adam--
Copy link
Contributor Author

Adam-- commented Jul 1, 2021

I'm closing this PR since it's growing quite old. Maybe in the future we can get some docs in.

@Adam-- Adam-- closed this Jul 1, 2021
@Adam-- Adam-- deleted the forms-navigation-docs branch July 1, 2021 13:07
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.

2 participants