Skip to content

fix: use require_relative in exe/ea#15

Merged
ronaldtse merged 3 commits into
mainfrom
fix/exe-require-relative
Jul 9, 2026
Merged

fix: use require_relative in exe/ea#15
ronaldtse merged 3 commits into
mainfrom
fix/exe-require-relative

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

Summary

Change require "ea" to require_relative "../lib/ea" in exe/ea, per project convention.

Verification

  • bundle exec rspec: 2036 examples, 0 failures, 37 pending
  • ea version: 0.2.1
  • ea spa plateau.qea -o out.html: 3.75 MB SPA generated successfully

ronaldtse added 3 commits July 9, 2026 08:50
Per project convention: executables use require_relative for the
initial library load instead of bare require. require_relative
../lib/ea ensures ea.rb (and its autoload entries) loads regardless
of gem activation state.
Three CI-breaking sibling-path dependencies in specs:

1. exe/ea: require_relative "../lib/ea" (was require "ea" — autoloads
   for Ea::Transformations weren't registered without the initial
   require).

2. spec/ea/transformations/parsers/xmi_parser_spec.rb: changed
   ../../../../lutaml-uml/examples/xmi/basic.xmi → fixtures_path("basic.xmi").
   The plateau XMI reference now has a skip guard.

3. spec/ea/diagram/svg_accuracy_spec.rb: added before(:all) skip guard
   for the sibling lutaml-uml reference SVG directory.

4. spec/ea/transformations/end_to_end_parsing_spec.rb: changed
   ../../../../lutaml-uml/examples/xmi/basic.xmi → local fixture path.

With lutaml-uml 0.5.1 on rubygems + ea gemspec pinned ~> 0.5, CI
should resolve all deps from rubygems and pass cleanly.

Suite: 2036 examples, 0 failures, 37 pending (unchanged).
Ruby 4.0 removed 'benchmark' from default gems. lib/ea/qea/benchmark.rb
requires it. Add as explicit runtime dependency.
@ronaldtse ronaldtse merged commit b707cdb into main Jul 9, 2026
11 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant