-
Notifications
You must be signed in to change notification settings - Fork 121
Add siteID and keyword attributes to Customer and CustomerSearchResult entities
#7860
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
Changes from 3 commits
2f312fd
017f527
352537a
312e9fd
761736b
db370f8
e08e392
07ae1ca
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 |
|---|---|---|
|
|
@@ -8,9 +8,9 @@ extension CustomerSearchResult { | |
| return NSFetchRequest<CustomerSearchResult>(entityName: "CustomerSearchResult") | ||
| } | ||
|
|
||
| @NSManaged public var customerID: Int64 | ||
| @NSManaged public var siteID: Int64 | ||
| @NSManaged public var keyword: String? | ||
|
||
| @NSManaged public var customers: Set<Customer>? | ||
|
|
||
| } | ||
|
|
||
| // MARK: Generated accessors for customers | ||
|
|
@@ -27,5 +27,4 @@ extension CustomerSearchResult { | |
|
|
||
| @objc(removeCustomers:) | ||
| @NSManaged public func removeFromCustomers(_ values: NSSet) | ||
|
|
||
| } | ||
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.
Yay inconsistent code generation... this isn't a problem, but this is what I meant when I mentioned that I'll often just run the generation to check it works, then revert it and add/update properties on the generated files so that the change is easier to see. No need to do anything, but it's a good practical example.