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

[feature] Clean warnings #11

Closed
wants to merge 80 commits into from
Closed

[feature] Clean warnings #11

wants to merge 80 commits into from

Conversation

alexmartinezm
Copy link
Contributor

Link to issue: #10

alexmartinezm and others added 30 commits February 24, 2019 12:35
…added LogHost in static context.""

This reverts commit 3d79dea.
Added log to print error messages.
Removed unnecessary validation for Password property.
alexmartinezm and others added 17 commits March 18, 2019 10:15
…validations-3

* master:
  Added comments on the iOS project following rule sets.
  Added comments and reordered code following analyzers rules.
  Added reference to Directory props from the src folder.
  Update directory.build.props

# Conflicts:
#	LICENSE
# Conflicts:
#	src/ReactiveUI.Validation/Contexts/ValidationContext.cs
@alexmartinezm alexmartinezm added the enhancement New feature or request label Mar 20, 2019
@alexmartinezm alexmartinezm self-assigned this Mar 20, 2019
@alexmartinezm alexmartinezm added this to In progress in Feature Smashing via automation Mar 20, 2019
@alexmartinezm alexmartinezm requested a review from a team March 20, 2019 12:27
@worldbeater
Copy link
Collaborator

worldbeater commented Mar 20, 2019

Looks good! By the way seeing a lot of commits unrelated to this PR. Those commits seem to be already merged to master, is there any chance to get rid of them (probably via rebase or force-pushing this particular branch)?

@glennawatson
Copy link
Collaborator

I think the fastest way Todo that would be to re clone the repo and paste these changes in from a backup copy.

@alexmartinezm
Copy link
Contributor Author

Those commits are from my last PR, which are not affecting the current PR's goal. So, how should we proceed with this PR now?

@glennawatson
Copy link
Collaborator

Handling in #13

Feature Smashing automation moved this from In progress to Done Mar 20, 2019
@lock
Copy link

lock bot commented Jun 24, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
Development

Successfully merging this pull request may close these issues.

None yet

3 participants