jbampton commented on code in PR #7562:
URL: https://github.com/apache/cloudstack/pull/7562#discussion_r3974548796


##########
.editorconfig:
##########
@@ -0,0 +1,26 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+# indent_size = 4
+indent_style = space

Review Comment:
   > I think we can add `trim_trailing_whitespace = true` also?
   
   We never finished the pre-commit work for all files with the "trailing 
whitespace" hook:
   
   
https://github.com/apache/cloudstack/blob/036493fd0149f8b3e639685be338ca5af2c6f1bd/.pre-commit-config.yaml#L185
   
   There is also the markdown line break concept:
   
   https://github.com/pre-commit/pre-commit-hooks#trailing-whitespace
   
   A quick regex search shows over 1200+ instances of the trailing whitespace 
in the codebase:
   
   <img width="821" height="205" alt="Screenshot 2026-09-10 at 10 59 25 am" 
src="https://github.com/user-attachments/assets/7427b662-4e64-4253-867a-206a2ccb211b";
 />
   



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to