documinty 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml ADDED
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA256:
3
+ metadata.gz: bcd92454896ed0ffc0ab3f3e86a064d71a62e2da5430fa1b7920aecac854ce6b
4
+ data.tar.gz: 740b56dd5581065c39d6cc09ff67c420867803d47c5420a5dfd4f8c682474616
5
+ SHA512:
6
+ metadata.gz: 47a1af0117416167328b171df5a3869adf2847f928a4d76f9a6c4c0c99661650929a42ded453e970760d1cee05d9bb1c8d22eeec65e48725e393865a24d73351
7
+ data.tar.gz: abdf028bb0da059b527b81198e4d7c00a6cc7fb71a4e6f31c5a97abecf059f69a4cb40216a8336377abc4650478f8270fc20bd96af8642defa8fc923b5d84aea
data/CHANGELOG.md ADDED
@@ -0,0 +1,5 @@
1
+ ## [Unreleased]
2
+
3
+ ## [0.1.0] - 2025-05-26
4
+
5
+ - Initial release
@@ -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) 2025 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,43 @@
1
+ # Documinty
2
+
3
+ TODO: Delete this and the text below, and describe your gem
4
+
5
+ Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/documinty`. To experiment with that code, run `bin/console` for an interactive prompt.
6
+
7
+ ## Installation
8
+
9
+ TODO: Replace `UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG` with your gem name right after releasing it to RubyGems.org. Please do not do it earlier due to security reasons. Alternatively, replace this section with instructions to install your gem from git if you don't plan to release to RubyGems.org.
10
+
11
+ Install the gem and add to the application's Gemfile by executing:
12
+
13
+ ```bash
14
+ bundle add UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG
15
+ ```
16
+
17
+ If bundler is not being used to manage dependencies, install the gem by executing:
18
+
19
+ ```bash
20
+ gem install UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG
21
+ ```
22
+
23
+ ## Usage
24
+
25
+ TODO: Write usage instructions here
26
+
27
+ ## Development
28
+
29
+ After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
30
+
31
+ To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
32
+
33
+ ## Contributing
34
+
35
+ Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/documinty. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/[USERNAME]/documinty/blob/main/CODE_OF_CONDUCT.md).
36
+
37
+ ## License
38
+
39
+ The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
40
+
41
+ ## Code of Conduct
42
+
43
+ Everyone interacting in the Documinty project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/documinty/blob/main/CODE_OF_CONDUCT.md).
data/exe/documinty ADDED
@@ -0,0 +1,6 @@
1
+ #!/usr/bin/env ruby
2
+
3
+ require "rubygems"
4
+
5
+ require "documinty"
6
+ Documinty::CLI.start(ARGV)
@@ -0,0 +1,145 @@
1
+ # lib/documinty/cli.rb
2
+ require 'thor'
3
+ require 'documinty/store'
4
+
5
+ module Documinty
6
+ class CLI < Thor
7
+ def self.exit_on_failure?
8
+ true
9
+ end
10
+
11
+ desc "init", "Initialize documinty in your project"
12
+ option :codebase, aliases: '-c', desc: 'Custom codebase name'
13
+ def init
14
+ store.init(codebase_name: options[:codebase])
15
+ end
16
+
17
+ desc "feature NAME", "Create a new feature for tagging"
18
+ def feature(name)
19
+ begin
20
+ store.add_feature(name)
21
+ say "✅ Created feature '#{name}'", :green
22
+ rescue Error => e
23
+ say "⚠️ #{e.message}", :red
24
+ end
25
+ end
26
+
27
+ desc "features", "List all defined features"
28
+ def features
29
+ fs = store.features
30
+ if fs.empty?
31
+ say "No features defined.", :yellow
32
+ else
33
+ say "Defined features:", :cyan
34
+ fs.each { |f| say "• #{f}", :green }
35
+ end
36
+ end
37
+
38
+ desc "document FILE", "Tag FILE under an existing feature"
39
+ option :feature, aliases: '-f', required: true, desc: 'Feature name to group under'
40
+ option :node, aliases: '-n', required: true, desc: 'Node/type label'
41
+ def document(path)
42
+ begin
43
+ entry = store.add_entry(
44
+ path: path,
45
+ node: options[:node],
46
+ feature: options[:feature],
47
+ timestamp: Time.now.iso8601,
48
+ description: options[:description] || ask("Enter a brief description for this node:")
49
+ )
50
+ say "✅ Documented #{entry['path']} as #{entry['node']} under '#{entry['feature']}'", :green
51
+ rescue Error => e
52
+ say "❌ #{e.message}", :red
53
+ exit(1)
54
+ end
55
+ end
56
+
57
+ desc "show FILE", "Display documentation for FILE (node & feature)"
58
+ def show_documented(path)
59
+ entries = store.entries_for(path)
60
+ if entries.empty?
61
+ say "❌ No documentation found for '#{path}'", :red
62
+ exit(1)
63
+ end
64
+
65
+ entries.each do |e|
66
+ say "File: #{e['path']}", :magenta
67
+ say "Node type: #{e['node']}", :magenta
68
+ say "Feature: #{e['feature']}", :magenta
69
+ say "Description: #{e['description']}", :magenta unless e['description'].to_s.empty?
70
+ say "Tagged at: #{e['timestamp']}", :magenta
71
+ say "-" * 40, :magenta
72
+ end
73
+ end
74
+
75
+ desc "untag FILE", "Remove FILE’s tag from an existing feature"
76
+ option :feature, aliases: '-f', required: true, desc: "Feature name"
77
+ def undocument(path)
78
+ begin
79
+ removed = store.remove_entry(path: path, feature: options[:feature])
80
+ removed.each do |e|
81
+ say "🗑️ Removed #{e['path']} (#{e['node'] || e['node_type']}) from '#{options[:feature]}'", :green
82
+ end
83
+ rescue Error => e
84
+ say "❌ #{e.message}", :red
85
+ exit(1)
86
+ end
87
+ end
88
+
89
+ desc "show-feature FEATURE", "List all files documented under FEATURE"
90
+ def show_feature(feature)
91
+ begin
92
+ entries = store.entries_for_feature(feature)
93
+ rescue Error => e
94
+ say "❌ #{e.message}", :red
95
+ exit(1)
96
+ end
97
+
98
+ if entries.empty?
99
+ say "No entries under '#{feature}'.", :red
100
+ else
101
+ say "Entries for '#{feature}':"
102
+ entries.each do |e|
103
+ say "• #{e['path']} (#{e['node']}) – #{e['description']}", :green
104
+ end
105
+ end
106
+ end
107
+
108
+ desc "show_feature_involved FEATURE", "Display files under FEATURE grouped by directory"
109
+ def show_feature_involved(feature)
110
+ begin
111
+ entries = store.entries_for_feature(feature)
112
+ rescue Error => e
113
+ say "❌ #{e.message}", :red
114
+ exit(1)
115
+ end
116
+
117
+ if entries.empty?
118
+ say "No entries under '#{feature}'.", :yellow
119
+ return
120
+ end
121
+
122
+ # Print the feature name in bold cyan
123
+ say "🔖 #{feature}", :cyan
124
+
125
+ # Group entries by their containing directory
126
+ grouped = entries.group_by { |e| File.dirname(e['path']) }
127
+
128
+ grouped.each do |dir, entries_in_dir|
129
+ # Print each directory line with a folder emoji, in green
130
+ say "📁 #{dir}", :green
131
+
132
+ entries_in_dir.each do |e|
133
+ # Print each filename line with a file emoji, indented, in green
134
+ say " 📄 #{File.basename(e['path'])}", :green
135
+ end
136
+ end
137
+ end
138
+
139
+ private
140
+
141
+ def store
142
+ @store ||= Store.new(Dir.pwd)
143
+ end
144
+ end
145
+ end
@@ -0,0 +1,116 @@
1
+ # lib/documinty/store.rb
2
+ require 'fileutils'
3
+ require 'yaml'
4
+ require 'time'
5
+
6
+ module Documinty
7
+ class Store
8
+ CONFIG_DIR = '.documinty'.freeze
9
+ CONFIG_FILE = 'config.yml'.freeze
10
+ FEATURES_DIR = 'features'.freeze
11
+ FEATURE_EXT = '.yml'.freeze
12
+
13
+ def initialize(root = Dir.pwd)
14
+ @root = root
15
+ @base_path = File.join(@root, CONFIG_DIR)
16
+ @features_path = File.join(@base_path, FEATURES_DIR)
17
+ end
18
+
19
+ # ─── bootstrap ────────────────────────────────────────────────────────────
20
+ # Create .documinty/, write config.yml, and make the features/ dir
21
+ def init(codebase_name: nil)
22
+ FileUtils.mkdir_p(@features_path)
23
+ cfg = { 'codebase_name' => (codebase_name || default_codebase_name) }
24
+ File.write(File.join(@base_path, CONFIG_FILE), cfg.to_yaml)
25
+ puts "✅ Initialized documinty at #{File.join(@root, CONFIG_DIR)}"
26
+ end
27
+
28
+ # ─── Features API ─────────────────────────────────────────────────────────
29
+ # Create a new feature file (errors if it already exists)
30
+ def add_feature(name)
31
+ path = feature_file(name)
32
+ raise Error, "Feature '#{name}' already exists" if File.exist?(path)
33
+
34
+ File.write(path, { 'entries' => [] }.to_yaml)
35
+ name
36
+ end
37
+
38
+ # List all defined feature names
39
+ def features
40
+ Dir.glob(File.join(@features_path, "*#{FEATURE_EXT}"))
41
+ .map { |f| File.basename(f, FEATURE_EXT) }
42
+ end
43
+
44
+ # ─── Entries API ──────────────────────────────────────────────────────────
45
+ # Tag a file under a specific feature
46
+ def add_entry(path:, node:, feature:, timestamp:, description: '')
47
+ file = feature_file(feature)
48
+ raise Error, "Feature '#{feature}' does not exist" unless File.exist?(file)
49
+
50
+ data = YAML.load_file(file) || {}
51
+ entries = (data['entries'] ||= [])
52
+ entry = {
53
+ 'path' => path,
54
+ 'node' => node.to_s,
55
+ 'feature' => feature,
56
+ 'description' => description.to_s.strip,
57
+ 'timestamp' => timestamp
58
+ }
59
+ entries << entry
60
+ File.write(file, data.to_yaml)
61
+ entry
62
+ end
63
+
64
+ # Return all entries across *all* features for a given file path
65
+ def entries_for(path)
66
+ results = []
67
+ features.each do |feature|
68
+ file = feature_file(feature)
69
+ next unless File.exist?(file)
70
+ data = YAML.load_file(file) || {}
71
+ (data['entries'] || []).each do |e|
72
+ if e['path'] == path
73
+ e['feature'] ||= feature
74
+ results << e
75
+ end
76
+ end
77
+ end
78
+ results
79
+ end
80
+
81
+ # Remove an entry for path under one feature
82
+ def remove_entry(path:, feature:)
83
+ file = feature_file(feature)
84
+ raise Error, "Feature '#{feature}' does not exist" unless File.exist?(file)
85
+
86
+ data = YAML.load_file(file) || {}
87
+ entries = data['entries'] || []
88
+ removed = entries.select { |e| e['path'] == path }
89
+ raise Error, "No entries for '#{path}' under feature '#{feature}'" if removed.empty?
90
+
91
+ data['entries'] = entries.reject { |e| e['path'] == path }
92
+ File.write(file, data.to_yaml)
93
+ removed
94
+ end
95
+
96
+ # Shows all the files listed under a feature
97
+ def entries_for_feature(feature)
98
+ file = feature_file(feature)
99
+ raise Error, "Feature '#{feature}' does not exist" unless File.exist?(file)
100
+
101
+ data = YAML.load_file(file) || {}
102
+ data['entries'] || []
103
+ end
104
+
105
+ private
106
+
107
+ # Build the path to a feature’s YAML file
108
+ def feature_file(name)
109
+ File.join(@features_path, "#{name}#{FEATURE_EXT}")
110
+ end
111
+
112
+ def default_codebase_name
113
+ File.basename(File.expand_path(@root))
114
+ end
115
+ end
116
+ end
@@ -0,0 +1,5 @@
1
+ # frozen_string_literal: true
2
+
3
+ module Documinty
4
+ VERSION = "0.2.0"
5
+ end
data/lib/documinty.rb ADDED
@@ -0,0 +1,10 @@
1
+ # frozen_string_literal: true
2
+
3
+ require "documinty/version"
4
+ require "documinty/cli"
5
+ require "documinty/store"
6
+
7
+ module Documinty
8
+ class Error < StandardError; end
9
+ # Your code goes here...
10
+ end
metadata ADDED
@@ -0,0 +1,81 @@
1
+ --- !ruby/object:Gem::Specification
2
+ name: documinty
3
+ version: !ruby/object:Gem::Version
4
+ version: 0.2.0
5
+ platform: ruby
6
+ authors:
7
+ - Marcel Carrero Pedre
8
+ bindir: exe
9
+ cert_chain: []
10
+ date: 2025-05-31 00:00:00.000000000 Z
11
+ dependencies:
12
+ - !ruby/object:Gem::Dependency
13
+ name: thor
14
+ requirement: !ruby/object:Gem::Requirement
15
+ requirements:
16
+ - - "~>"
17
+ - !ruby/object:Gem::Version
18
+ version: '1.2'
19
+ type: :runtime
20
+ prerelease: false
21
+ version_requirements: !ruby/object:Gem::Requirement
22
+ requirements:
23
+ - - "~>"
24
+ - !ruby/object:Gem::Version
25
+ version: '1.2'
26
+ - !ruby/object:Gem::Dependency
27
+ name: rspec
28
+ requirement: !ruby/object:Gem::Requirement
29
+ requirements:
30
+ - - "~>"
31
+ - !ruby/object:Gem::Version
32
+ version: '3.0'
33
+ type: :development
34
+ prerelease: false
35
+ version_requirements: !ruby/object:Gem::Requirement
36
+ requirements:
37
+ - - "~>"
38
+ - !ruby/object:Gem::Version
39
+ version: '3.0'
40
+ description: This gem will enable developers to document their classes and features
41
+ email:
42
+ - marcel.pedre001@outlook.com
43
+ executables:
44
+ - documinty
45
+ extensions: []
46
+ extra_rdoc_files: []
47
+ files:
48
+ - CHANGELOG.md
49
+ - CODE_OF_CONDUCT.md
50
+ - LICENSE.txt
51
+ - README.md
52
+ - exe/documinty
53
+ - lib/documinty.rb
54
+ - lib/documinty/cli.rb
55
+ - lib/documinty/store.rb
56
+ - lib/documinty/version.rb
57
+ homepage: https://github.com/yourusername/carreromarcel
58
+ licenses:
59
+ - MIT
60
+ metadata:
61
+ homepage_uri: https://github.com/yourusername/carreromarcel
62
+ source_code_uri: https://github.com/yourusername/carreromarcel
63
+ changelog_uri: https://github.com/yourusername/carreromarcel/blob/main/CHANGELOG.md
64
+ rdoc_options: []
65
+ require_paths:
66
+ - lib
67
+ required_ruby_version: !ruby/object:Gem::Requirement
68
+ requirements:
69
+ - - ">="
70
+ - !ruby/object:Gem::Version
71
+ version: 3.1.0
72
+ required_rubygems_version: !ruby/object:Gem::Requirement
73
+ requirements:
74
+ - - ">="
75
+ - !ruby/object:Gem::Version
76
+ version: '0'
77
+ requirements: []
78
+ rubygems_version: 3.6.2
79
+ specification_version: 4
80
+ summary: A codebase auto documentation tool.
81
+ test_files: []