Bug 12478 - Autoformatting of enums broken
Summary: Autoformatting of enums broken
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 4.0.8
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: 4.0.9 (from master)
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2013-05-30 12:20 UTC by oppixp
Modified: 2013-06-24 16:18 UTC (History)
1 user (show)

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

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 FIXED

Description oppixp 2013-05-30 12:20:57 UTC
The autoformatter moves the comma in an enum declaration to the beginning of the next line.

Starting from XS 4.05 the auto formatting does not work well anymore. :(

The formatted code looks like this:

namespace Library.Engine.Enums
{
  /// <summary>
  /// Fader state.
  /// </summary>
  public enum FaderState
  {
    /// <summary>
    /// Idle.
    /// </summary>
    Idle
,

    /// <summary>
    /// Fade in.
    /// </summary>
    FadeIn
,

    /// <summary>
    /// Fade out.
    /// </summary>
    FadeOut
  }
}
Comment 1 Mike Krüger 2013-05-31 00:12:49 UTC
Should be already fixed
Comment 2 PJ 2013-06-24 16:18:36 UTC
This bug was marked as fixed for Xamarin Studio 4.0.9, which is currently in the beta channel. Try it out!