1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
//! # Node.js Repository Abstractions
//!
//! ## What
//! This file defines the traits and abstractions for working with Node.js
//! repositories in a unified way. It provides the `RepositoryInfo` trait that
//! enables consistent access to repository information regardless of whether
//! the repository is a simple project or a complex monorepo structure.
//!
//! ## How
//! The module defines traits that establish contracts for repository behavior.
//! The `RepositoryInfo` trait provides a common interface that can be implemented
//! by different repository types, enabling polymorphic handling of various
//! Node.js project structures while maintaining type safety and consistency.
//!
//! ## Why
//! A unified repository interface is essential for building tools that work
//! across different Node.js project types. This abstraction layer allows
//! code to work with repositories generically, without needing to know the
//! specific implementation details of simple projects vs. monorepos.
use Path;
use ;
/// Common interface for all Node.js repository types.
///
/// This trait provides a unified API for accessing repository information
/// regardless of whether it's a simple repository or a monorepo. All
/// repository implementations must provide these basic capabilities to
/// enable consistent tooling and processing.
///
/// The trait focuses on the fundamental characteristics that all Node.js
/// repositories share: location, type identification, and package management
/// configuration. More specific functionality is handled by dedicated
/// implementations.
///
/// # Examples
///
/// ```
/// use sublime_standard_tools::node::{RepositoryInfo, RepoKind};
/// use std::path::Path;
///
/// fn analyze_repository(repo: &impl RepositoryInfo) {
/// println!("Repository root: {}", repo.root().display());
/// println!("Repository type: {}", repo.kind().name());
///
/// if repo.kind().is_monorepo() {
/// println!("This is a monorepo with multiple packages");
/// } else {
/// println!("This is a simple repository");
/// }
///
/// if let Some(manager) = repo.package_manager() {
/// println!("Package manager: {}", manager.command());
/// }
/// }
/// ```
///
/// # Implementation Guidelines
///
/// When implementing this trait:
/// - `root()` should return the absolute path to the repository root
/// - `kind()` should reflect the actual repository structure detected
/// - `package_manager()` should return None if detection failed or was disabled
/// - All methods should be consistent with the repository's actual state