markdown_tree 0.1.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/.standard.yml +3 -0
- data/CHANGELOG.md +5 -0
- data/CODE_OF_CONDUCT.md +132 -0
- data/LICENSE.txt +21 -0
- data/README.md +84 -0
- data/Rakefile +10 -0
- data/lib/markdown_tree/version.rb +5 -0
- data/lib/markdown_tree.rb +46 -0
- data/sig/markdown_tree.rbs +4 -0
- metadata +64 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA256:
|
3
|
+
metadata.gz: 80c589374873d6426d2de3a445ac43861cc2e6a9dc601aef2333bdad76b03569
|
4
|
+
data.tar.gz: 1e3ff7583d53a28c58fde933d69f3cb3062d0c3ccb203c9faddf20821e8e682b
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: f15388e828bdc99e83670ae660d82d66b446d34ee0b3ce2405eaa2f311abab9a0d503ece311eb7e3a3d580449a2d9cafb700c6ffc60d8f801f88aece66c3010e
|
7
|
+
data.tar.gz: 40bea3084e3fec4c7b1e6e474db49595dc66b1787b1d87713e96f10e76ede80609cf75cb0e63a8944de3efc6bb9691b7c2d6b9a13a0efb513769b14e4a258fda
|
data/.standard.yml
ADDED
data/CHANGELOG.md
ADDED
data/CODE_OF_CONDUCT.md
ADDED
@@ -0,0 +1,132 @@
|
|
1
|
+
# Contributor Covenant Code of Conduct
|
2
|
+
|
3
|
+
## Our Pledge
|
4
|
+
|
5
|
+
We as members, contributors, and leaders pledge to make participation in our
|
6
|
+
community a harassment-free experience for everyone, regardless of age, body
|
7
|
+
size, visible or invisible disability, ethnicity, sex characteristics, gender
|
8
|
+
identity and expression, level of experience, education, socio-economic status,
|
9
|
+
nationality, personal appearance, race, caste, color, religion, or sexual
|
10
|
+
identity and orientation.
|
11
|
+
|
12
|
+
We pledge to act and interact in ways that contribute to an open, welcoming,
|
13
|
+
diverse, inclusive, and healthy community.
|
14
|
+
|
15
|
+
## Our Standards
|
16
|
+
|
17
|
+
Examples of behavior that contributes to a positive environment for our
|
18
|
+
community include:
|
19
|
+
|
20
|
+
* Demonstrating empathy and kindness toward other people
|
21
|
+
* Being respectful of differing opinions, viewpoints, and experiences
|
22
|
+
* Giving and gracefully accepting constructive feedback
|
23
|
+
* Accepting responsibility and apologizing to those affected by our mistakes,
|
24
|
+
and learning from the experience
|
25
|
+
* Focusing on what is best not just for us as individuals, but for the overall
|
26
|
+
community
|
27
|
+
|
28
|
+
Examples of unacceptable behavior include:
|
29
|
+
|
30
|
+
* The use of sexualized language or imagery, and sexual attention or advances of
|
31
|
+
any kind
|
32
|
+
* Trolling, insulting or derogatory comments, and personal or political attacks
|
33
|
+
* Public or private harassment
|
34
|
+
* Publishing others' private information, such as a physical or email address,
|
35
|
+
without their explicit permission
|
36
|
+
* Other conduct which could reasonably be considered inappropriate in a
|
37
|
+
professional setting
|
38
|
+
|
39
|
+
## Enforcement Responsibilities
|
40
|
+
|
41
|
+
Community leaders are responsible for clarifying and enforcing our standards of
|
42
|
+
acceptable behavior and will take appropriate and fair corrective action in
|
43
|
+
response to any behavior that they deem inappropriate, threatening, offensive,
|
44
|
+
or harmful.
|
45
|
+
|
46
|
+
Community leaders have the right and responsibility to remove, edit, or reject
|
47
|
+
comments, commits, code, wiki edits, issues, and other contributions that are
|
48
|
+
not aligned to this Code of Conduct, and will communicate reasons for moderation
|
49
|
+
decisions when appropriate.
|
50
|
+
|
51
|
+
## Scope
|
52
|
+
|
53
|
+
This Code of Conduct applies within all community spaces, and also applies when
|
54
|
+
an individual is officially representing the community in public spaces.
|
55
|
+
Examples of representing our community include using an official email address,
|
56
|
+
posting via an official social media account, or acting as an appointed
|
57
|
+
representative at an online or offline event.
|
58
|
+
|
59
|
+
## Enforcement
|
60
|
+
|
61
|
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
62
|
+
reported to the community leaders responsible for enforcement at
|
63
|
+
[INSERT CONTACT METHOD].
|
64
|
+
All complaints will be reviewed and investigated promptly and fairly.
|
65
|
+
|
66
|
+
All community leaders are obligated to respect the privacy and security of the
|
67
|
+
reporter of any incident.
|
68
|
+
|
69
|
+
## Enforcement Guidelines
|
70
|
+
|
71
|
+
Community leaders will follow these Community Impact Guidelines in determining
|
72
|
+
the consequences for any action they deem in violation of this Code of Conduct:
|
73
|
+
|
74
|
+
### 1. Correction
|
75
|
+
|
76
|
+
**Community Impact**: Use of inappropriate language or other behavior deemed
|
77
|
+
unprofessional or unwelcome in the community.
|
78
|
+
|
79
|
+
**Consequence**: A private, written warning from community leaders, providing
|
80
|
+
clarity around the nature of the violation and an explanation of why the
|
81
|
+
behavior was inappropriate. A public apology may be requested.
|
82
|
+
|
83
|
+
### 2. Warning
|
84
|
+
|
85
|
+
**Community Impact**: A violation through a single incident or series of
|
86
|
+
actions.
|
87
|
+
|
88
|
+
**Consequence**: A warning with consequences for continued behavior. No
|
89
|
+
interaction with the people involved, including unsolicited interaction with
|
90
|
+
those enforcing the Code of Conduct, for a specified period of time. This
|
91
|
+
includes avoiding interactions in community spaces as well as external channels
|
92
|
+
like social media. Violating these terms may lead to a temporary or permanent
|
93
|
+
ban.
|
94
|
+
|
95
|
+
### 3. Temporary Ban
|
96
|
+
|
97
|
+
**Community Impact**: A serious violation of community standards, including
|
98
|
+
sustained inappropriate behavior.
|
99
|
+
|
100
|
+
**Consequence**: A temporary ban from any sort of interaction or public
|
101
|
+
communication with the community for a specified period of time. No public or
|
102
|
+
private interaction with the people involved, including unsolicited interaction
|
103
|
+
with those enforcing the Code of Conduct, is allowed during this period.
|
104
|
+
Violating these terms may lead to a permanent ban.
|
105
|
+
|
106
|
+
### 4. Permanent Ban
|
107
|
+
|
108
|
+
**Community Impact**: Demonstrating a pattern of violation of community
|
109
|
+
standards, including sustained inappropriate behavior, harassment of an
|
110
|
+
individual, or aggression toward or disparagement of classes of individuals.
|
111
|
+
|
112
|
+
**Consequence**: A permanent ban from any sort of public interaction within the
|
113
|
+
community.
|
114
|
+
|
115
|
+
## Attribution
|
116
|
+
|
117
|
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
|
118
|
+
version 2.1, available at
|
119
|
+
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
|
120
|
+
|
121
|
+
Community Impact Guidelines were inspired by
|
122
|
+
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
|
123
|
+
|
124
|
+
For answers to common questions about this code of conduct, see the FAQ at
|
125
|
+
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
|
126
|
+
[https://www.contributor-covenant.org/translations][translations].
|
127
|
+
|
128
|
+
[homepage]: https://www.contributor-covenant.org
|
129
|
+
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
|
130
|
+
[Mozilla CoC]: https://github.com/mozilla/diversity
|
131
|
+
[FAQ]: https://www.contributor-covenant.org/faq
|
132
|
+
[translations]: https://www.contributor-covenant.org/translations
|
data/LICENSE.txt
ADDED
@@ -0,0 +1,21 @@
|
|
1
|
+
The MIT License (MIT)
|
2
|
+
|
3
|
+
Copyright (c) 2024 TODO: Write your name
|
4
|
+
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
7
|
+
in the Software without restriction, including without limitation the rights
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
10
|
+
furnished to do so, subject to the following conditions:
|
11
|
+
|
12
|
+
The above copyright notice and this permission notice shall be included in
|
13
|
+
all copies or substantial portions of the Software.
|
14
|
+
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
21
|
+
THE SOFTWARE.
|
data/README.md
ADDED
@@ -0,0 +1,84 @@
|
|
1
|
+
# MarkdownTree
|
2
|
+
|
3
|
+
**MarkdownTree** is a Ruby gem that generates a directory structure in Markdown format. It is highly configurable, allowing you to exclude specific folders, choose the root directory, and specify the output file name.
|
4
|
+
|
5
|
+
## Installation
|
6
|
+
|
7
|
+
You can install the gem and add it to your application's Gemfile by executing:
|
8
|
+
|
9
|
+
```bash
|
10
|
+
bundle add markdown_tree
|
11
|
+
```
|
12
|
+
|
13
|
+
If bundler is not being used to manage dependencies, install the gem by executing:
|
14
|
+
|
15
|
+
```bash
|
16
|
+
gem install markdown_tree
|
17
|
+
```
|
18
|
+
|
19
|
+
## Usage
|
20
|
+
|
21
|
+
### Basic Example
|
22
|
+
|
23
|
+
To generate the directory structure in Markdown format from the current directory, simply call the `generate_tree` method:
|
24
|
+
|
25
|
+
```ruby
|
26
|
+
require 'markdown_tree'
|
27
|
+
|
28
|
+
MarkdownTree.generate_tree
|
29
|
+
```
|
30
|
+
|
31
|
+
### Excluding Specific Folders
|
32
|
+
|
33
|
+
You can configure which folders to exclude from the generated structure:
|
34
|
+
|
35
|
+
```ruby
|
36
|
+
MarkdownTree.configure do |config|
|
37
|
+
config.exclude_list = ['node_modules', '.git', 'tmp']
|
38
|
+
end
|
39
|
+
|
40
|
+
MarkdownTree.generate_tree
|
41
|
+
```
|
42
|
+
|
43
|
+
### Selecting the Root Directory
|
44
|
+
|
45
|
+
You can also specify the directory from which you want to generate the structure:
|
46
|
+
|
47
|
+
```ruby
|
48
|
+
MarkdownTree.configure do |config|
|
49
|
+
config.root_directory = '/path/to/your/directory'
|
50
|
+
end
|
51
|
+
|
52
|
+
MarkdownTree.generate_tree
|
53
|
+
```
|
54
|
+
|
55
|
+
### Customizing the Output File Name
|
56
|
+
|
57
|
+
You can set the name of the file where the directory structure will be saved:
|
58
|
+
|
59
|
+
```ruby
|
60
|
+
MarkdownTree.configure do |config|
|
61
|
+
config.output_file = 'custom_directory_structure.md'
|
62
|
+
end
|
63
|
+
|
64
|
+
MarkdownTree.generate_tree
|
65
|
+
```
|
66
|
+
|
67
|
+
### Full Configuration Example in Rails
|
68
|
+
|
69
|
+
If you're using Rails, you can configure all these options in an initializer:
|
70
|
+
|
71
|
+
```ruby
|
72
|
+
# config/initializers/markdown_tree.rb
|
73
|
+
MarkdownTree.configure do |config|
|
74
|
+
config.exclude_list = ['node_modules', '.git', 'tmp'] # Directories to exclude
|
75
|
+
config.root_directory = Rails.root.join('app').to_s # Root directory to start generating structure
|
76
|
+
config.output_file = 'custom_directory_structure.md' # Output file name
|
77
|
+
end
|
78
|
+
```
|
79
|
+
|
80
|
+
## Contributing
|
81
|
+
Contribution directions go here. You can fork the repository, create a new branch, and submit a pull request for review. Please make sure to write tests for your contributions and follow the coding standards set in the project.
|
82
|
+
|
83
|
+
## License
|
84
|
+
The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
|
data/Rakefile
ADDED
@@ -0,0 +1,46 @@
|
|
1
|
+
require "markdown_tree/version"
|
2
|
+
require "markdown_tree/configuration"
|
3
|
+
require "markdown_tree/railtie" if defined?(Rails)
|
4
|
+
|
5
|
+
module MarkdownTree
|
6
|
+
class << self
|
7
|
+
def generate_tree(directory = nil)
|
8
|
+
directory ||= configuration.root_directory || Dir.pwd
|
9
|
+
|
10
|
+
File.open(configuration.output_file, "w") do |file|
|
11
|
+
process_directory(directory, file)
|
12
|
+
end
|
13
|
+
end
|
14
|
+
|
15
|
+
private
|
16
|
+
|
17
|
+
def process_directory(directory, file, prefix = "")
|
18
|
+
items = Dir.entries(directory) - [".", ".."]
|
19
|
+
|
20
|
+
items.reject! { |item| configuration.exclude_list.include?(item) }
|
21
|
+
|
22
|
+
items.each_with_index do |item, index|
|
23
|
+
path = File.join(directory, item)
|
24
|
+
is_last = index == items.size - 1
|
25
|
+
connector = is_last ? "└── " : "├── "
|
26
|
+
|
27
|
+
file.puts "#{prefix}#{connector}#{item}"
|
28
|
+
|
29
|
+
if File.directory?(path)
|
30
|
+
new_prefix = prefix + (is_last ? " " : "│ ")
|
31
|
+
process_directory(path, file, new_prefix)
|
32
|
+
end
|
33
|
+
end
|
34
|
+
end
|
35
|
+
|
36
|
+
def configuration
|
37
|
+
@configuration ||= Configuration.new
|
38
|
+
end
|
39
|
+
end
|
40
|
+
|
41
|
+
configure do |config|
|
42
|
+
config.exclude_list = ["node_modules", ".git", ".DS_Store"]
|
43
|
+
config.root_directory = Dir.pwd
|
44
|
+
config.output_file = "directory_structure.md"
|
45
|
+
end
|
46
|
+
end
|
metadata
ADDED
@@ -0,0 +1,64 @@
|
|
1
|
+
--- !ruby/object:Gem::Specification
|
2
|
+
name: markdown_tree
|
3
|
+
version: !ruby/object:Gem::Version
|
4
|
+
version: 0.1.0
|
5
|
+
platform: ruby
|
6
|
+
authors:
|
7
|
+
- aemabit
|
8
|
+
autorequire:
|
9
|
+
bindir: exe
|
10
|
+
cert_chain: []
|
11
|
+
date: 2024-08-28 00:00:00.000000000 Z
|
12
|
+
dependencies: []
|
13
|
+
description: |-
|
14
|
+
MarkdownTree is designed for developers and teams who need a simple and flexible way to document the structure of their projects. Whether you are preparing a README, documenting a codebase, or generating a project overview, MarkdownTree allows you to create a clear and organized representation of your directory structure in Markdown format.
|
15
|
+
|
16
|
+
With MarkdownTree, you can:
|
17
|
+
- Exclude specific folders or files from the generated structure.
|
18
|
+
- Define the root directory from which to start generating the structure.
|
19
|
+
- Customize the output file name to fit your documentation standards.
|
20
|
+
|
21
|
+
MarkdownTree integrates seamlessly with Rails and other Ruby applications, offering an initializer for easy configuration. It is a valuable tool for maintaining clear and up-to-date project documentation.
|
22
|
+
email:
|
23
|
+
- am@connectnodes.io
|
24
|
+
executables: []
|
25
|
+
extensions: []
|
26
|
+
extra_rdoc_files: []
|
27
|
+
files:
|
28
|
+
- ".standard.yml"
|
29
|
+
- CHANGELOG.md
|
30
|
+
- CODE_OF_CONDUCT.md
|
31
|
+
- LICENSE.txt
|
32
|
+
- README.md
|
33
|
+
- Rakefile
|
34
|
+
- lib/markdown_tree.rb
|
35
|
+
- lib/markdown_tree/version.rb
|
36
|
+
- sig/markdown_tree.rbs
|
37
|
+
homepage: https://github.com/aemabit/markdown_tree
|
38
|
+
licenses:
|
39
|
+
- MIT
|
40
|
+
metadata:
|
41
|
+
allowed_push_host: https://rubygems.org
|
42
|
+
homepage_uri: https://github.com/aemabit/markdown_tree
|
43
|
+
source_code_uri: https://github.com/aemabit/markdown_tree
|
44
|
+
changelog_uri: https://github.com/aemabit/markdown_tree/blob/main/CHANGELOG.md
|
45
|
+
post_install_message:
|
46
|
+
rdoc_options: []
|
47
|
+
require_paths:
|
48
|
+
- lib
|
49
|
+
required_ruby_version: !ruby/object:Gem::Requirement
|
50
|
+
requirements:
|
51
|
+
- - ">="
|
52
|
+
- !ruby/object:Gem::Version
|
53
|
+
version: 3.0.0
|
54
|
+
required_rubygems_version: !ruby/object:Gem::Requirement
|
55
|
+
requirements:
|
56
|
+
- - ">="
|
57
|
+
- !ruby/object:Gem::Version
|
58
|
+
version: '0'
|
59
|
+
requirements: []
|
60
|
+
rubygems_version: 3.5.11
|
61
|
+
signing_key:
|
62
|
+
specification_version: 4
|
63
|
+
summary: Generates a directory structure in Markdown format.
|
64
|
+
test_files: []
|