Repository navigation
V2 toMany relation structure support in V3 #152
Description
Activity
- changed the title
[-]ToMany relations completely broken in v3[/-][+]ToMany relations are completely broken in v3[/+]on Feb 21, 2019 Hi @Anakros
This data structure is actually correct but our quickstart might mislead you.
Before
@canner/cli v3.1.1, the blog example we used has one-to-many relationship on post and category. In other words, a category can only have one post and a post can have many categories. That's why you saw apostIdon category data. That's how we achieveone-to-manyrelationship.We found it bizarre and misleading as an official example, so we changed it to
many-to-manyrelationship atv3.1.1, so afterv3.1.1, your data structure in firebase will look like this:
You can see that to achieve many-to-many relationship, we have other two tables saving relationships from both side.
So, don't worry. Nothing is broken here. We have large amount of tests on relationship.
Simply upgrade to latest version, you'll see what you expect.Thanks!
Hi @Anakros
As we announced in our blog post: https://www.cannercms.com/blog/2019/02/07/canner-v3#migration-from-canner-v2-v3
We'll release a new feature next week allows you to create the exact same structure in v2 using
mode: embed.<relation keyName="categories" ui="multipleSelect" title="categories" relation={{type: 'toMany', to: 'categories', mode: 'embed'}} uiParams={{ columns: [{ title: 'Name', dataIndex: 'name' }] }} />
We'll also publish a migration guide for developers to transform from v2 to v3. I'll mention you in this thread as well.
If it's okay, I'd like to change the title to
V2 toMany relation structure support in V3since the wordcompletely brokenmight scare our users 😅- changed the title
[-]ToMany relations are completely broken in v3[/-][+]V2 toMany relation structure support in V3[/+]on Feb 22, 2019 @Anakros regarding deployment to Firebase, We'll add a section in document as well next week that teach people how to deploy to Firebase Cloud Function.
Since our architecture includes GraphQL Server and the Authentication server, it's easier to deploy the whole thing to Cloud Function.
@Anakros There are still some optimization details (for example the cloud function bundle size) we're trying out here. We really want developers to have the best experience using Canner.
We plan to publish a blog post approximately next Tuesday if it's okay.
Thanks!
Thanks, looking forward to it!
Steps to reproduce: follow the quick start tutorial here, select blog template, optionally configure firebase/firestore datasource, try to add multiple objects in
<relation>field and take a look at the database structure.Currently the structure look like this:
Categories
Posts
As we can see Canner creates not even different relation type, but for completely wrong schema too. It happens for all types of the data source: memory, firebase, firestore.
How could this happen?