Opened on 02/24/2016 at 04:56:58 PM
Closed on 09/27/2016 at 07:17:53 PM
#3693 closed change (fixed)
Create standard EditorConfig for ABP projects
| Reported by: | juliandoucette | Assignee: | juliandoucette |
|---|---|---|---|
| Priority: | Unknown | Milestone: | |
| Module: | Automation | Keywords: | |
| Cc: | fhd, saroyanm, greiner, trev, erikvold | Blocked By: | |
| Blocking: | Platform: | Unknown / Cross platform | |
| Ready: | yes | Confidential: | no |
| Tester: | Unknown | Verified working: | no |
| Review URL(s): | |||
Description (last modified by juliandoucette)
Background
- We have very specific code style standards for ABP projects
- Documentation on our code style is spread across multiple documents and sometimes missing
What to change
We should create a standard EditorConfig for all projects to help reduce the time spent on code style related NITs in code review
EditorConfig is different from JSCS and ESLint because it sets the default settings in your editor of choice to help avoid common style inconsistencies without linting. It also works with multiple programming languages.
Attachments (0)
Change History (5)
comment:2 Changed on 06/15/2016 at 01:14:10 PM by juliandoucette
- Component changed from Unknown to Build-and-Release-Tools
- Owner set to juliandoucette
- Ready set
comment:3 Changed on 06/15/2016 at 01:19:21 PM by juliandoucette
- Review URL(s) modified (diff)
- Status changed from new to reviewing
comment:4 Changed on 09/27/2016 at 02:34:38 PM by abpbot
comment:5 Changed on 09/27/2016 at 07:17:53 PM by juliandoucette
- Resolution set to fixed
- Status changed from reviewing to closed
Note: See
TracTickets for help on using
tickets.
A commit referencing this issue has landed:
Issue 3693 - Created global editorconfig