Uh oh!
There was an error while loading. Please reload this page.
Refactoring RepositoryForm Validators - #2395
Conversation
| await SafeRepositoryNameWarningValidator.ResetAsync(); | ||
| RepositoryName = name; | ||
| }); | ||
| // this.WhenAny(x => x.SelectedConnection, x => x.SelectedAccount, |
There was a problem hiding this comment.
We should delete these comments!
Uh oh!
There was an error while loading. Please reload this page.
| string SafeRepositoryName { get; } | ||
| ReactivePropertyValidator<string> RepositoryNameValidator { get; } | ||
| ReactivePropertyValidator<string> SafeRepositoryNameWarningValidator { get; } | ||
| ReactivePropertyValidator<(string repositoryName, IConnection connection, IAccount account)> RepositoryNameValidator { get; } |
There was a problem hiding this comment.
Looking at the code, I can't see where we're using the connection or account for validation. I wonder if once upon a time we were checking for an existing repository with the same name as part of the validation? It looks like this check is now done and the error surfaced when the user attempts to create the repository.
I think we might be able to simplify this to use just the repositoryName. I'm wondering if the buggy code was actually completely obsolete. ;-)
jcansdale
left a comment
There was a problem hiding this comment.
I'm wondering if we could simply remove the buggy code?
See comment:
#2395 (review)
No description provided.