Refactor Schemas into LinkedDataFragments Namespace #39
Conversation
Adds a generic Guardfile. `spec_helper.rb` includes a stub on `Setting` in a before(:each), which prevents various spec files from running without the rest of the suite. This pattern also has the issue that it stubs `Setting#cache_backend` without warning to developers, giving unexpected results. We should find a way to remove it. See #38. In the meanwhile, we introduce a guard to prevent errors, and allow modules that don't depend on `Setting` to be tested independently.
Replaces `app` schemas with those in `lib`. This breaks backward compatibility for any clients referring directly to the schema constants. It's otherwise a simple refactor.
This is the first step in a refactoring to move schemas to lib. Adds tests for the schemas.
|
Is this in reference to #38 so that you can run individual tests? |
|
@scande3: It's the first step in a stepwise refactor to move core logic to I'm submitting them in the small refactors like this to keep review sane and ensure we avoid breaking changes. #38 was encountered along the way. The aggressive stubbing made it hard to extract |
|
The first follow-up is here: The best public branch for where things are going is: https://github.com/ActiveTriples/linked-data-fragments/commits/feature/rack-server |
Moves Schemas into
libas a first step in isolating other logic.