Skip to content
This repository was archived by the owner on May 1, 2024. It is now read-only.

Fix setting for spaces after using and lock keywords #14

Merged
merged 1 commit into from
Mar 25, 2016

Conversation

hartez
Copy link
Contributor

@hartez hartez commented Mar 24, 2016

Description of Change

Correct the shared Resharper settings for spaces after using and lock.

@kingces95
Copy link
Contributor

👍

@kingces95
Copy link
Contributor

For XML documents can we use spaces instead of tabs? XML documents are heavily indented and so if tabs are used instead of spaces then the wrapping on GitHub is pretty bad.

@kingces95
Copy link
Contributor

  • Search and replace using( with using (

@kingces95
Copy link
Contributor

Guess we should squash this one..

@hartez hartez force-pushed the resharper_spaces branch from fd8e11a to e541081 Compare March 25, 2016 19:29
@jassmith jassmith merged commit ec06759 into master Mar 25, 2016
@rmarinho rmarinho deleted the resharper_spaces branch March 29, 2016 17:19
jsuarezruiz pushed a commit to PlainConcepts/Xamarin.Forms that referenced this pull request Sep 7, 2017
@samhouts samhouts added this to the 2.2.0 milestone Jul 3, 2018
shyunMin pushed a commit to shyunMin/Xamarin.Forms that referenced this pull request Dec 11, 2020
mattleibow added a commit that referenced this pull request Jan 28, 2021
* Initial work to add a FileSystem API

* Added some FileSystem API tests

* Use "Package" instead of "Bundle"

* Using NSSearchPath instead of NSFileManager

* We are using spaces instead of tabs

* Added the FileSystem sample

* Fixing styles

* We cache NOTHING

* Added docs

* removing UserDataDirectory as this is just an iOS thing

* Use char not string for the replace

* iOS should always have a path, but if it doesn't, don't throw, just return null

* Using the new exceptions

* Fixing the exceptions for the tests
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants