You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.adoc
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -695,7 +695,7 @@ be concise, but won't carry much meaning).
695
695
But what to do about all the other namespaces out there that don't have idiomatic aliases? Well, you better be consistent in your approach to deriving aliases for them,
696
696
otherwise the people working on a shared Clojure codebase are going to experience a great deal of confusion. Here are a few rules that you should follow.footnote:[These guidelines are based on a https://stuartsierra.com/2015/05/10/clojure-namespace-aliases[blog post] by Stuart Sierra.]
697
697
698
-
. Make the alias the same as the namespace name with the leading parts removed.
698
+
1. Make the alias the same as the namespace name with the leading parts removed.
699
699
700
700
[source,clojure]
701
701
----
@@ -705,7 +705,7 @@ otherwise the people working on a shared Clojure codebase are going to experienc
705
705
[clojure.string :as string]))
706
706
----
707
707
708
-
. Keep enough trailing parts to make each alias unique.
708
+
2. Keep enough trailing parts to make each alias unique.
709
709
710
710
[source,clojure]
711
711
----
@@ -715,7 +715,7 @@ otherwise the people working on a shared Clojure codebase are going to experienc
715
715
716
716
TIP: Yes, namespace aliases can have dots in them. Make good use of them.
717
717
718
-
. Eliminate redundant words such as "core" and "clj" in aliases.
718
+
3. Eliminate redundant words such as "core" and "clj" in aliases.
0 commit comments