Skip to content

Commit f19ad68

Browse files
authored
Update README.md
1 parent 5b3e02d commit f19ad68

1 file changed

Lines changed: 8 additions & 4 deletions

File tree

README.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,17 +13,21 @@ A brand new Swift abstraction layer for CoreData's original interface
1313
[![License](https://img.shields.io/cocoapods/l/Reloaded.svg?style=flat)](http://cocoapods.org/pods/Reloaded)
1414

1515

16-
##
17-
18-
> <b style="color:red;">Warning! - *Project is not yet completely finished. We are going to release an alpha version in April, contact us on Slack for ETA or follow the status below*</b>
19-
2016
## Setup data model
2117

2218
Well, this is exactly the same process as you would do when setting up core data the old way. If you haven't created your app from a template, just:
2319
* create a new **Data Model** file
2420
* give it the same name as your bundle has (Reloaded is trying to use `kCFBundleNameKey` to generate the expected name)
2521
* Create your entities as you would
2622

23+
> You can also override the default container name for use in multi-target apps using `CoreData.fallbackContainerName`
24+
25+
```swift
26+
/// Fallback container name, overrides bundle name globally
27+
/// Use in multitarget apps with shared model
28+
public static var fallbackContainerName: String?
29+
```
30+
2731
## Basic usage
2832

2933
> If you don't have your data model <i>(.xcdatamodeld)</i> file yet, jump to the [Setup data model](#setup-data-model) section and then come back.

0 commit comments

Comments
 (0)