Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: Sencha Architect 3.2: 'name' property in metadata changes with each save

  1. #1
    Sencha Premium Member
    Join Date
    Nov 2013
    Location
    Tolmin, Slovenia
    Posts
    43
    Answers
    1

    Question Answered: Sencha Architect 3.2: 'name' property in metadata changes with each save

    We have a ExtJS 4.2.3 project that was initially created with SA 3.0.

    Project contains a few customised button classes that are used in different places in the UI.

    After upgrading to 3.2, a 'name' property of these buttons in metadata files changes each time the project is saved.

    Code:
    @@ -252,7 +252,7 @@
                             "layout|flex": null,
                             "text": "xt_cancel"
                         },
    -                    "name": "mediumbutton15",
    +                    "name": "mediumbutton6",
                         "designerId": "873ff414-2416-44eb-a246-3d1dccf3342f",
                         "masterInstanceId": "66037ddd-4469-4647-aeec-3ad4d160f14b"
                     },
    @@ -267,7 +267,7 @@
                             "itemId": "finishAccountRequest",
                             "text": "xt_activateAccount"
                         },
    -                    "name": "mediumbutton16",
    +                    "name": "mediumbutton7",
                         "designerId": "89a6c73f-1393-43f6-9b31-355ddb42fb30",
                         "masterInstanceId": "66037ddd-4469-4647-aeec-3ad4d160f14b"
    There is no way that these names would be set in the SA 3.2 UI.

    This is very annoying because we have to filter out files that don't contain meaningful changes before committing them to git.

    Is there a solution for this?

    Thanks,

    Matej Kenda

  2. No need to look. I got the steps. The issue is logged in our system under DSGNR-6770

    Thank you for the help with clarifying the problem

  3. #2
    Sencha Premium Member
    Join Date
    Sep 2014
    Posts
    25
    Answers
    1

    Default sencha architect 'name' change is painful in version control

    I also noticed that renaming and did not yet find a solution.

    Version control is much more difficult with these constant useless changes in the meta data files.
    Please sencha development fix this...

  4. #3
    Sencha Premium Member
    Join Date
    Nov 2013
    Location
    Tolmin, Slovenia
    Posts
    43
    Answers
    1

    Default

    Just for FYI: this issue is still present in SA 3.5.

  5. #4
    Sencha Premium Member
    Join Date
    Sep 2014
    Posts
    25
    Answers
    1

    Default Yes still the same problem ... loosing time every checkin ...

    It's now an everydays procedure - checking the files marked as different and reverting all those which are only name changes.

    2 years using the tool (~160 productive days) times about 3 checkin's per day. Costs 60 seconds to check the files of a project with about 60 classes.

    400 Minutes wasted. ~ 7 hours Thanks sencha for wasting my time.

  6. #5
    Sencha User
    Join Date
    Sep 2014
    Location
    Central Europe
    Posts
    795
    Answers
    103

    Default

    Hello

    Thank you for your report. It seems that the project metadata files become somehow corrupted when you upgraded from 3.0 ?

    I assume that you work with your old projects. Is this by any chance reproducible from the plain project with SA 3.2 or 3.5 ?

    The name config in your metadata file is duplicated. It should not be like this.
    I would try to delete one name config. Make sure that the value in the name config is unique in the whole project (search the metadata files).

    Don't forget the backup your project before any changes!

    Regards
    Petr

  7. #6
    Sencha Premium Member
    Join Date
    Nov 2013
    Location
    Tolmin, Slovenia
    Posts
    43
    Answers
    1

    Default

    The 'name' is not duplicated. What I pasted is a portion of a diff for one of the files.Files were created with 3.0 and then upgraded to 3.1 and 3.2, where we experienced this problem for the first time.Problem persists in 3.5 also.I'll see if I can prepare a simple example to demonstrate what is happening.

  8. #7
    Sencha Premium Member
    Join Date
    Nov 2013
    Location
    Tolmin, Slovenia
    Posts
    43
    Answers
    1

    Default

    The name property is automatically generated by Architect when saving the project. There is no name in the custom Button class or the linked instances in Architect UI to be set. On each save, these might get different values.

  9. #8
    Sencha Premium Member
    Join Date
    Nov 2013
    Location
    Tolmin, Slovenia
    Posts
    43
    Answers
    1

    Default

    I managed to reproduce the problem with SA 3.5 and ExtJS 6.0.2.

    There are two snapshots in the attached file.

    In the first, a special button is created and linked to a few views.

    Then a form is added containing some special buttons and linked to the same view.

    name property was changed by SA when saving the project.

    Code:
    $ diff -u metadata-saved-1/view/MyViewport metadata-saved-2/view/MyViewport
    --- metadata-saved-1/view/MyViewport    2016-04-27 18:41:35.000000000 +0200
    +++ metadata-saved-2/view/MyViewport    2016-04-27 21:22:03.000000000 +0200
    @@ -68,7 +68,7 @@
                                             "itemId": "button1",
                                             "text": "Button One"
                                         },
    -                                    "name": "specialbutton",
    +                                    "name": "specialbutton2",
                                         "designerId": "051d9cda-6e35-4c91-a206-5bb4507af81b",
                                         "masterInstanceId": "dcaa67ef-66bd-4264-b5ef-2743e24bb7ae"
                                     },
    @@ -83,7 +83,7 @@
                                             "itemId": "button2",
                                             "text": "Button Two"
                                         },
    -                                    "name": "specialbutton1",
    +                                    "name": "specialbutton3",
                                         "designerId": "093cafdf-870a-4671-802f-c359eb4a0b6a",
                                         "masterInstanceId": "dcaa67ef-66bd-4264-b5ef-2743e24bb7ae"
                                     }
    @@ -92,6 +92,17 @@
    I hope that this helps to understand the problem.
    Attached Files Attached Files

  10. #9
    Sencha Premium Member
    Join Date
    Sep 2014
    Posts
    25
    Answers
    1

    Default my problem is not the duplication, it's the changing numbers in the name!

    thought that was the original meaning of this thread.

    Anyway -- upgrading from architect 3.2 to 3.5 and upgrading Exits 5.1.2 to Extjs 6 was a mess.
    I spend nearly a week to get everything running again.

    After days I figured out, that architect is not generating half of the JS classes because of a corrupt ".architect" file ... I simply deleted the file and also all files in build-folder and started the Architect from scratch. After this I opened each file of the project and saved it. (Save all did not work correctly!).

    Now my project is working as expected.

  11. #10
    Sencha Premium Member
    Join Date
    Nov 2013
    Location
    Tolmin, Slovenia
    Posts
    43
    Answers
    1

    Default

    Problem is changing the name. I never stated otherwise. I posted output of "diff" between before and after to demonstrate the problem.


    For those that don't know that, diff is a tool for comparing text files on the command line. That technique is also used inside git to identify the differences to commit.

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •