mirrors/bisq
1
0
Fork 0
mirror of https://github.com/bisq-network/bisq.git synced 2024-11-19 09:52:23 +01:00
Code Issues Packages Projects Releases Wiki Activity
1504e4992a
bisq/.idea/codeStyles/Project.xml

180 lines
8.8 KiB
XML
Raw Normal View History

Organize imports This change adds a .idea/codeStyles/Project.xml file that orders all imports from higher-level layers to lower-level layers, with blank lines between different major packages. The purpose of this approach is to allow the reader to scan the imports in a file efficiently to understand what kind of work the class does, what layers it touches, and so forth. Keeping imports clean and ordered by layer can be a powerful tool in keeping a codebase well organized and tangle-free over time. bisq.* packages are always sorted at the top.
2018-03-12 15:21:02 +01:00
<component name="ProjectCodeStyleConfiguration">
<code_scheme name="Project" version="173">
<HTMLCodeStyleSettings>
<option name="HTML_ATTRIBUTE_WRAP" value="0" />
<option name="HTML_TEXT_WRAP" value="0" />
<option name="HTML_ALIGN_ATTRIBUTES" value="false" />
</HTMLCodeStyleSettings>
<JavaCodeStyleSettings>
<option name="CLASS_COUNT_TO_USE_IMPORT_ON_DEMAND" value="99" />
<option name="NAMES_COUNT_TO_USE_IMPORT_ON_DEMAND" value="5" />
<option name="PACKAGES_TO_USE_IMPORT_ON_DEMAND">
<value />
</option>
<option name="IMPORT_LAYOUT_TABLE">
<value>
<package name="bisq.monitor" withSubpackages="true" static="false" />
<emptyLine />
Organize imports with common layout (bisq-network/style#2)
2018-03-14 21:02:11 +01:00
<package name="bisq.price" withSubpackages="true" static="false" />
<emptyLine />
<package name="bisq.statistics" withSubpackages="true" static="false" />
<emptyLine />
<package name="bisq.seednode" withSubpackages="true" static="false" />
<emptyLine />
<package name="bisq.desktop" withSubpackages="true" static="false" />
<emptyLine />
Organize imports This change adds a .idea/codeStyles/Project.xml file that orders all imports from higher-level layers to lower-level layers, with blank lines between different major packages. The purpose of this approach is to allow the reader to scan the imports in a file efficiently to understand what kind of work the class does, what layers it touches, and so forth. Keeping imports clean and ordered by layer can be a powerful tool in keeping a codebase well organized and tangle-free over time. bisq.* packages are always sorted at the top.
2018-03-12 15:21:02 +01:00
<package name="bisq.core" withSubpackages="true" static="false" />
<emptyLine />
<package name="bisq.network" withSubpackages="true" static="false" />
<emptyLine />
<package name="bisq.common" withSubpackages="true" static="false" />
<emptyLine />
<package name="io.bisq.generated" withSubpackages="true" static="false" />
<emptyLine />
<package name="com.google.protobuf" withSubpackages="true" static="false" />
<emptyLine />
<package name="net.gpedro.integrations.slack" withSubpackages="true" static="false" />
<emptyLine />
Organize imports with common layout (bisq-network/style#2)
2018-03-14 21:02:11 +01:00
<package name="org.knowm.xchange" withSubpackages="true" static="false" />
Organize imports This change adds a .idea/codeStyles/Project.xml file that orders all imports from higher-level layers to lower-level layers, with blank lines between different major packages. The purpose of this approach is to allow the reader to scan the imports in a file efficiently to understand what kind of work the class does, what layers it touches, and so forth. Keeping imports clean and ordered by layer can be a powerful tool in keeping a codebase well organized and tangle-free over time. bisq.* packages are always sorted at the top.
2018-03-12 15:21:02 +01:00
<emptyLine />
<package name="org.libdohj" withSubpackages="true" static="false" />
<emptyLine />
<package name="org.bitcoinj" withSubpackages="true" static="false" />
<emptyLine />
<package name="com.neemre.btcdcli4j" withSubpackages="true" static="false" />
<emptyLine />
<package name="net.glxn.qrgen" withSubpackages="true" static="false" />
<emptyLine />
Organize imports with common layout (bisq-network/style#2)
2018-03-14 21:02:11 +01:00
<package name="org.springframework" withSubpackages="true" static="false" />
<emptyLine />
Organize imports This change adds a .idea/codeStyles/Project.xml file that orders all imports from higher-level layers to lower-level layers, with blank lines between different major packages. The purpose of this approach is to allow the reader to scan the imports in a file efficiently to understand what kind of work the class does, what layers it touches, and so forth. Keeping imports clean and ordered by layer can be a powerful tool in keeping a codebase well organized and tangle-free over time. bisq.* packages are always sorted at the top.
2018-03-12 15:21:02 +01:00
<package name="org.apache.http" withSubpackages="true" static="false" />
<emptyLine />
Organize imports with common layout (bisq-network/style#2)
2018-03-14 21:02:11 +01:00
<package name="javax.servlet" withSubpackages="true" static="false" />
<emptyLine />
Organize imports This change adds a .idea/codeStyles/Project.xml file that orders all imports from higher-level layers to lower-level layers, with blank lines between different major packages. The purpose of this approach is to allow the reader to scan the imports in a file efficiently to understand what kind of work the class does, what layers it touches, and so forth. Keeping imports clean and ordered by layer can be a powerful tool in keeping a codebase well organized and tangle-free over time. bisq.* packages are always sorted at the top.
2018-03-12 15:21:02 +01:00
<package name="org.berndpruenster.netlayer" withSubpackages="true" static="false" />
<emptyLine />
<package name="com.runjva" withSubpackages="true" static="false" />
<emptyLine />
Organize imports with common layout (bisq-network/style#2)
2018-03-14 21:02:11 +01:00
<package name="com.googlecode.jcsv" withSubpackages="true" static="false" />
<emptyLine />
<package name="com.fasterxml.jackson" withSubpackages="true" static="false" />
Organize imports This change adds a .idea/codeStyles/Project.xml file that orders all imports from higher-level layers to lower-level layers, with blank lines between different major packages. The purpose of this approach is to allow the reader to scan the imports in a file efficiently to understand what kind of work the class does, what layers it touches, and so forth. Keeping imports clean and ordered by layer can be a powerful tool in keeping a codebase well organized and tangle-free over time. bisq.* packages are always sorted at the top.
2018-03-12 15:21:02 +01:00
<emptyLine />
<package name="com.google.gson" withSubpackages="true" static="false" />
<emptyLine />
Organize imports with common layout (bisq-network/style#2)
2018-03-14 21:02:11 +01:00
<package name="org.json.simple" withSubpackages="true" static="false" />
Organize imports This change adds a .idea/codeStyles/Project.xml file that orders all imports from higher-level layers to lower-level layers, with blank lines between different major packages. The purpose of this approach is to allow the reader to scan the imports in a file efficiently to understand what kind of work the class does, what layers it touches, and so forth. Keeping imports clean and ordered by layer can be a powerful tool in keeping a codebase well organized and tangle-free over time. bisq.* packages are always sorted at the top.
2018-03-12 15:21:02 +01:00
<emptyLine />
<package name="joptsimple" withSubpackages="true" static="false" />
<emptyLine />
<package name="com.google.inject" withSubpackages="true" static="false" />
<emptyLine />
<package name="javax.inject" withSubpackages="true" static="false" />
<emptyLine />
<package name="com.google.common" withSubpackages="true" static="false" />
<emptyLine />
<package name="org.apache.commons" withSubpackages="true" static="false" />
<emptyLine />
Update imports for de.jensd.fx and optimize imports
2018-04-17 11:17:35 +02:00
<package name="de.jensd.fx" withSubpackages="true" static="false" />
Organize imports This change adds a .idea/codeStyles/Project.xml file that orders all imports from higher-level layers to lower-level layers, with blank lines between different major packages. The purpose of this approach is to allow the reader to scan the imports in a file efficiently to understand what kind of work the class does, what layers it touches, and so forth. Keeping imports clean and ordered by layer can be a powerful tool in keeping a codebase well organized and tangle-free over time. bisq.* packages are always sorted at the top.
2018-03-12 15:21:02 +01:00
<emptyLine />
<package name="org.controlsfx" withSubpackages="true" static="false" />
<emptyLine />
<package name="org.reactfx" withSubpackages="true" static="false" />
<emptyLine />
<package name="javafx.application" withSubpackages="true" static="false" />
<emptyLine />
<package name="javafx.fxml" withSubpackages="true" static="false" />
<emptyLine />
<package name="javafx.animation" withSubpackages="true" static="false" />
<emptyLine />
<package name="javafx.stage" withSubpackages="true" static="false" />
<emptyLine />
<package name="javafx.scene" withSubpackages="true" static="false" />
<emptyLine />
<package name="com.sun.javafx.scene" withSubpackages="true" static="false" />
<emptyLine />
<package name="com.sun.javafx.tk.quantum" withSubpackages="true" static="false" />
<emptyLine />
<package name="javafx.css" withSubpackages="true" static="false" />
<emptyLine />
<package name="com.sun.javafx.css" withSubpackages="true" static="false" />
<emptyLine />
<package name="javafx.geometry" withSubpackages="true" static="false" />
<emptyLine />
<package name="org.fxmisc.easybind" withSubpackages="true" static="false" />
<emptyLine />
<package name="javafx.beans" withSubpackages="true" static="false" />
<emptyLine />
<package name="javafx.event" withSubpackages="true" static="false" />
<emptyLine />
<package name="javafx.collections" withSubpackages="true" static="false" />
<emptyLine />
<package name="com.sun.javafx.collections" withSubpackages="true" static="false" />
<emptyLine />
<package name="javafx.util" withSubpackages="true" static="false" />
<emptyLine />
<package name="java.awt" withSubpackages="true" static="false" />
<emptyLine />
<package name="javax.imageio" withSubpackages="true" static="false" />
<emptyLine />
<package name="org.spongycastle" withSubpackages="true" static="false" />
<emptyLine />
<package name="org.bouncycastle" withSubpackages="true" static="false" />
<emptyLine />
<package name="javax.crypto" withSubpackages="true" static="false" />
<emptyLine />
Organize imports with common layout (bisq-network/style#2)
2018-03-14 21:02:11 +01:00
<package name="java.security" withSubpackages="true" static="false" />
Organize imports This change adds a .idea/codeStyles/Project.xml file that orders all imports from higher-level layers to lower-level layers, with blank lines between different major packages. The purpose of this approach is to allow the reader to scan the imports in a file efficiently to understand what kind of work the class does, what layers it touches, and so forth. Keeping imports clean and ordered by layer can be a powerful tool in keeping a codebase well organized and tangle-free over time. bisq.* packages are always sorted at the top.
2018-03-12 15:21:02 +01:00
<emptyLine />
Organize imports with common layout (bisq-network/style#2)
2018-03-14 21:02:11 +01:00
<package name="java.time" withSubpackages="true" static="false" />
<emptyLine />
<package name="java.text" withSubpackages="true" static="false" />
Organize imports This change adds a .idea/codeStyles/Project.xml file that orders all imports from higher-level layers to lower-level layers, with blank lines between different major packages. The purpose of this approach is to allow the reader to scan the imports in a file efficiently to understand what kind of work the class does, what layers it touches, and so forth. Keeping imports clean and ordered by layer can be a powerful tool in keeping a codebase well organized and tangle-free over time. bisq.* packages are always sorted at the top.
2018-03-12 15:21:02 +01:00
<emptyLine />
<package name="javax.net" withSubpackages="true" static="false" />
<emptyLine />
<package name="java.net" withSubpackages="true" static="false" />
<emptyLine />
Organize imports with common layout (bisq-network/style#2)
2018-03-14 21:02:11 +01:00
<package name="java.nio" withSubpackages="true" static="false" />
Organize imports This change adds a .idea/codeStyles/Project.xml file that orders all imports from higher-level layers to lower-level layers, with blank lines between different major packages. The purpose of this approach is to allow the reader to scan the imports in a file efficiently to understand what kind of work the class does, what layers it touches, and so forth. Keeping imports clean and ordered by layer can be a powerful tool in keeping a codebase well organized and tangle-free over time. bisq.* packages are always sorted at the top.
2018-03-12 15:21:02 +01:00
<emptyLine />
Organize imports with common layout (bisq-network/style#2)
2018-03-14 21:02:11 +01:00
<package name="java.io" withSubpackages="true" static="false" />
Organize imports This change adds a .idea/codeStyles/Project.xml file that orders all imports from higher-level layers to lower-level layers, with blank lines between different major packages. The purpose of this approach is to allow the reader to scan the imports in a file efficiently to understand what kind of work the class does, what layers it touches, and so forth. Keeping imports clean and ordered by layer can be a powerful tool in keeping a codebase well organized and tangle-free over time. bisq.* packages are always sorted at the top.
2018-03-12 15:21:02 +01:00
<emptyLine />
<package name="java.math" withSubpackages="true" static="false" />
<emptyLine />
Organize imports with common layout (bisq-network/style#2)
2018-03-14 21:02:11 +01:00
<package name="java.util" withSubpackages="true" static="false" />
<emptyLine />
Organize imports This change adds a .idea/codeStyles/Project.xml file that orders all imports from higher-level layers to lower-level layers, with blank lines between different major packages. The purpose of this approach is to allow the reader to scan the imports in a file efficiently to understand what kind of work the class does, what layers it touches, and so forth. Keeping imports clean and ordered by layer can be a powerful tool in keeping a codebase well organized and tangle-free over time. bisq.* packages are always sorted at the top.
2018-03-12 15:21:02 +01:00
<package name="java.lang" withSubpackages="true" static="false" />
<emptyLine />
<package name="org.slf4j" withSubpackages="true" static="false" />
<emptyLine />
<package name="ch.qos.logback" withSubpackages="true" static="false" />
<emptyLine />
<package name="lombok" withSubpackages="true" static="false" />
<emptyLine />
<package name="org.jetbrains.annotations" withSubpackages="true" static="false" />
<emptyLine />
<package name="javax.annotation" withSubpackages="true" static="false" />
<emptyLine />
<package name="com.natpryce.makeiteasy" withSubpackages="true" static="false" />
<emptyLine />
<package name="org.powermock" withSubpackages="true" static="false" />
<emptyLine />
<package name="mockit" withSubpackages="true" static="false" />
<emptyLine />
<package name="org.junit" withSubpackages="true" static="false" />
<emptyLine />
<package name="" withSubpackages="true" static="true" />
<emptyLine />
<emptyLine />
<emptyLine />
<package name="" withSubpackages="true" static="false" />
</value>
</option>
</JavaCodeStyleSettings>
Preserve blank lines in .properties files This setting is actually necessary only in bisq-common, but it has been added to the shared codeStyles/Project.xml in bisq-network/dao so as to be able to copy the same configuration file to all bisq-* projects.
2018-03-16 11:37:29 +01:00
<Properties>
<option name="KEEP_BLANK_LINES" value="true" />
</Properties>
Organize imports This change adds a .idea/codeStyles/Project.xml file that orders all imports from higher-level layers to lower-level layers, with blank lines between different major packages. The purpose of this approach is to allow the reader to scan the imports in a file efficiently to understand what kind of work the class does, what layers it touches, and so forth. Keeping imports clean and ordered by layer can be a powerful tool in keeping a codebase well organized and tangle-free over time. bisq.* packages are always sorted at the top.
2018-03-12 15:21:02 +01:00
<codeStyleSettings language="JAVA">
Wrap lines automatically at 120 character margin Problem: bisq-network/style#3 indicates code should be wrapped at 120 characters, but it is likely that people will forget and that this habit will only change slowly. Solution: Configure IDEA to wrap lines automatically when typing past 120 characters, forcing the reminder to happen in real time. If this becomes a nuisance, we can remove it later. Note that this change also explicitly sets the RIGHT_MARGIN value to 120, even though this is already IDEA's default value. This is simply to be explicit and self-documenting.
2018-03-16 11:40:33 +01:00
<option name="RIGHT_MARGIN" value="120" />
Organize imports This change adds a .idea/codeStyles/Project.xml file that orders all imports from higher-level layers to lower-level layers, with blank lines between different major packages. The purpose of this approach is to allow the reader to scan the imports in a file efficiently to understand what kind of work the class does, what layers it touches, and so forth. Keeping imports clean and ordered by layer can be a powerful tool in keeping a codebase well organized and tangle-free over time. bisq.* packages are always sorted at the top.
2018-03-12 15:21:02 +01:00
<option name="BLANK_LINES_BEFORE_PACKAGE" value="1" />
Disable IDEA wrap on typing See bisq-network/style#3
2018-03-23 23:29:57 +01:00
<option name="WRAP_ON_TYPING" value="0" />
Add visual guide at 90-character Javadoc margin Per bisq-network/style#5
2018-03-16 11:57:23 +01:00
<option name="SOFT_MARGINS" value="90" />
Organize imports This change adds a .idea/codeStyles/Project.xml file that orders all imports from higher-level layers to lower-level layers, with blank lines between different major packages. The purpose of this approach is to allow the reader to scan the imports in a file efficiently to understand what kind of work the class does, what layers it touches, and so forth. Keeping imports clean and ordered by layer can be a powerful tool in keeping a codebase well organized and tangle-free over time. bisq.* packages are always sorted at the top.
2018-03-12 15:21:02 +01:00
</codeStyleSettings>
</code_scheme>
Normalize .idea/codeStyles/*.xml EOF newlines IDEA does strips EOF newlines in these files, so this commit adds an exception to the usual rule about inserting them. This will avoid spurious whitespace diffs on these files in the future.
2018-03-16 11:33:38 +01:00
</component>
Reference in New Issue Copy Permalink