Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Seeding from existing project loses library info #970

Closed
brollb opened this issue Apr 22, 2016 · 2 comments
Closed

Seeding from existing project loses library info #970

brollb opened this issue Apr 22, 2016 · 2 comments
Assignees
@kecso
Labels
Enhancement GME Libraries Major
Milestone
v2.0.0

Comments

@brollb
Copy link
Contributor

brollb commented Apr 22, 2016

When creating a new project from a seed (that is an existing project), library information is lost (turned into regular nodes and errors)
@pmeijer pmeijer added this to the v2.0.0 milestone Apr 25, 2016
@pmeijer
Copy link
Contributor

pmeijer commented Apr 25, 2016 •
edited

This is targeted for 2.0.0, in the meanwhile duplicate should work or export/import with webgmex.

kecso added a commit that referenced this issue May 3, 2016
@kecso
#970 library info lost if seeding from existing project
73e102c 
- the seed from existing project now also uses the raw format
@kecso kecso self-assigned this May 3, 2016
pmeijer pushed a commit that referenced this issue May 4, 2016
@kecso
#970 library info lost if seeding from existing project (#986)
0d39f46 
- the seed from existing project now also uses the raw format
@pmeijer
Copy link
Contributor

pmeijer commented May 6, 2016

Closed by #986

@pmeijer pmeijer closed this as completed May 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kecso kecso

Labels
Enhancement GME Libraries Major
Projects
None yet
Milestone
v2.0.0
Development

No branches or pull requests
3 participants
@kecso @brollb @pmeijer