-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Accept static_model_preferences class name as string #4070
Closed
willianveiga
wants to merge
1
commit into
solidusio:master
from
willianveiga:feature/accept-static-model-preferences-class-names-as-string
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,7 +5,7 @@ | |
module Spree | ||
RSpec.describe Preferences::StaticModelPreferences do | ||
let(:preference_class) do | ||
Class.new do | ||
MyFakeStaticModelPreferencesClass ||= Class.new do | ||
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. I think defining a constant here will actually define it under |
||
include Preferences::Preferable | ||
preference :color, :string | ||
end | ||
|
@@ -23,6 +23,11 @@ module Spree | |
expect(definitions).to have_key('my_definition') | ||
end | ||
|
||
it "can add with string class name" do | ||
subject.add(preference_class.to_s, 'my_definition', {}) | ||
expect(definitions).to have_key('my_definition') | ||
end | ||
|
||
it "errors assigning invalid preferences" do | ||
expect { | ||
subject.add(preference_class, 'my_definition', { ice_cream: 'chocolate' }) | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
This will trigger an autoload during initialization, which is one of the things that this change should avoid. Thoughts on just converting to a string if it's not already and allowing
Definition
to accept it as well?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.
Hey @elia, I'm wondering how to fix it. In the end,
add
creates anotherDefinition
instance, and it calls.defined_preferences
on the class 🤷