Bug 4823 - Apply policy ruins the formatting
Summary: Apply policy ruins the formatting
Status: RESOLVED ANSWERED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 2.9.x
Hardware: PC Linux
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2012-05-02 11:24 UTC by Jaapjan
Modified: 2016-01-15 20:47 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Demo case (3.09 KB, application/zip)
2012-05-02 11:24 UTC, Jaapjan
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED ANSWERED

Description Jaapjan 2012-05-02 11:24:43 UTC
Created attachment 1794 [details]
Demo case

Open solution, apply policy and indenting is broken / code looks horrible (especially in larger files).
Comment 1 Mike Krüger 2012-05-02 11:33:15 UTC
Formats correctly for mre.

What is 'apply policy' ?
Which formatting policy did you apply ?
Comment 2 Jaapjan 2012-05-02 13:56:34 UTC
Demonstration screencast

http://www.screenr.com/heC8
Comment 3 PJ 2013-11-19 16:32:23 UTC
This bug was targeted for a past milestone, moving to the next active milestone.
Comment 5 Mike Krüger 2016-01-15 20:47:09 UTC
In 6.0 we're using a way more advanced formatter - so I would say it's fixed