-
Notifications
You must be signed in to change notification settings - Fork 119
[Discussion] Put files into buckets of responsibilities/seams #145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 4 commits
3a8b828
6fcd8a5
e46b253
896797e
ac57f56
009df05
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| ### Configurations | ||
|
|
||
| Includes validators which are outside of primary `check` runs. | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| # Extracting references | ||
|
|
||
| - Given a `AST::Node`, this module extracts `Packwerk::Reference`. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If you put it like this, it sounds like everything here works in the context of a single node. However, |
||
| - `Packwerk::Reference` contains `constant` information, that are worked by `Inflector`. | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,6 +4,7 @@ | |
| require "ast/node" | ||
|
|
||
| module Packwerk | ||
| # from file path to node | ||
| class FileProcessor | ||
| class UnknownFileTypeResult < Offense | ||
| def initialize(file:) | ||
|
|
@@ -20,6 +21,7 @@ def call(file_path) | |
| parser = @parser_factory.for_path(file_path) | ||
| return [UnknownFileTypeResult.new(file: file_path)] if parser.nil? | ||
|
|
||
| # path to node | ||
| node = File.open(file_path, "r", external_encoding: Encoding::UTF_8) do |file| | ||
| parser.call(io: file, file_path: file_path) | ||
| rescue Parsers::ParseError => e | ||
|
|
@@ -31,6 +33,7 @@ def call(file_path) | |
| node_processor = @node_processor_factory.for(filename: file_path, node: node) | ||
| node_visitor = Packwerk::NodeVisitor.new(node_processor: node_processor) | ||
|
|
||
| # node to offence | ||
| node_visitor.visit(node, ancestors: [], result: result) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, the content of this conditional doesn't really seem to fit here. I'd rather just hand off to something that processes the AST instead of instantiating processors and visitors here. |
||
| end | ||
| result | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,6 +4,8 @@ | |
| require "constant_resolver" | ||
|
|
||
| module Packwerk | ||
| # Packwerk used to run as a part of Rubocop. | ||
| # Now that Packwerk is a standalone script, this structure shouldn't be necessary. | ||
| class RunContext | ||
| extend T::Sig | ||
|
|
||
|
|
@@ -52,7 +54,32 @@ def initialize( | |
|
|
||
| sig { params(file: String).returns(T::Array[T.nilable(::Packwerk::Offense)]) } | ||
| def process_file(file:) | ||
| file_processor.call(file) | ||
| # 1. file path to node | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. it's more like file path to AST, but that contains nodes, so... you're not wrong |
||
| # It needs to return ancestors relative to node | ||
| node, ancestors = file_processor.call(file) | ||
|
|
||
| # Inside NodeProcessor - @reference_extractor.reference_from_node(node, ancestors: ancestors, file_path: @filename) | ||
| # 2. node to constant | ||
| # 3. constant to reference | ||
| @constant_name_inspectors.each do |inspector| | ||
| constant_name = inspector.constant_name_from_node(node, ancestors: ancestors) | ||
| break if constant_name | ||
| end | ||
|
|
||
| reference_from_constant(constant_name, node: node, ancestors: ancestors, file_path: file_path) if constant_name | ||
|
||
|
|
||
| # Inside NodeProcessor | ||
| # 4. reference to an offence | ||
| @checkers.each_with_object([]) do |checker, violations| | ||
| next unless checker.invalid_reference?(reference) | ||
| offense = Packwerk::ReferenceOffense.new( | ||
| location: Node.location(node), | ||
| reference: reference, | ||
| violation_type: checker.violation_type | ||
| ) | ||
| violations << offense | ||
| end | ||
|
Comment on lines
+57
to
+97
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If we will divide code's responsibility by their explicit "steps", something needs to have the responsibility of orchestration.
Does this direction make sense to you guys? @exterm @dougedey-shopify
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can we eliminate
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yup, certainly! I'll first focus on isolating the responsibilities of data transformation within the |
||
|
|
||
| end | ||
|
|
||
| private | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would probably go with the comment in https://github.com/Shopify/packwerk/pull/144/files#diff-5ca9dcd54fd0b9eeef94e00ba6adc7822dc83e5dd2bfb9e8d96fd3c356de8b8aR10-R11