Skip to content

Comments

#92 changed variant editor to use new package.manifest format, #91 added null check on attribute group#93

Open
jamiehowarth0 wants to merge 1 commit intoTeaCommerce:masterfrom
jamiehowarth0:master
Open

#92 changed variant editor to use new package.manifest format, #91 added null check on attribute group#93
jamiehowarth0 wants to merge 1 commit intoTeaCommerce:masterfrom
jamiehowarth0:master

Conversation

@jamiehowarth0
Copy link

Tested & now persists to dataNtext in cmsPropertyData.

… & now persists to dataNtext in cmsPropertyData.
@jamiehowarth0 jamiehowarth0 changed the title #92 changed variant editor to use new package.manifest format #92 changed variant editor to use new package.manifest format, #91 added null check on attribute group Sep 24, 2019
@mattbrailsford
Copy link
Contributor

@benjaminhowarth1 have you checked what happens as part of an upgrade? does the data get moved over? or do we still need to implement that?

Also, can you re-target your PR to be against the dev branch?

Really nice work fella 👍

@jamiehowarth0
Copy link
Author

Data migration will need writing, I haven't had a chance to address that yet.

@jamiehowarth0
Copy link
Author

Proof of concept to migrate data from nvarchar to ntext in cmsPropertyData: https://gist.github.com/benjaminhowarth1/2e94c7cb0747cd9854cbb0987322d5f6

@mattbrailsford
Copy link
Contributor

@benjaminhowarth1 looks good to me. Some awesome work here fella 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants