{"push_id":3144197083,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"dcc0a14e6b81a675b26c7729bb21ce282ded0d6b","before":"95781493ed6df14cb30153e747c0a4baa0589d8d","commits":[{"sha":"dcc0a14e6b81a675b26c7729bb21ce282ded0d6b","author":{"name":"Syed Irtaza Raza","email":"a69610f8cf9664cf3beb0437617a0cae59cd96e3@grakn.ai"},"message":"bug fixes (#4737)\n\nWhy is this PR needed?\r\nSub-typed schema concepts were connected to inherited attributes\r\nUser was able to add an inherited attribute when defining a sup-typed schema concept causing duplicated attributes\r\nRemoving an attribute of a schema concept which is sup-typing the same attribute would remove the \"sub\" edge as well\r\nDeleting a schema concept which had subbed schema concepts produced an error\r\nDeleting multiple schema concepts only deleted the first one selected\r\nWhat does the PR do?\r\nDo not construct edges between schema concepts and inherited attributes\r\nHighlight inherited attributes by default when defining a sup-typed schema concept\r\nCheck if we are removing only the \"has\" edge when unhasing an attribute from a schema concept\r\nRefine the error message shown when deleting a subbed schema concept\r\nDo not allow deleting of multiple schema concepts at once (show error)\r\nDoes it break backwards compatibility?\r\nNo\r\n\r\nList of future improvements not on this PR\r\nModularise the has and plays panels with all their functionalities in a separate component and reuse in NewEntityPanel, NewAttributePanel, and NewRelationshipPanel\r\nAdd tests for missing schema designer actions","distinct":true,"url":"https://api.github.com/repos/graknlabs/grakn/commits/dcc0a14e6b81a675b26c7729bb21ce282ded0d6b"}]}
{"actor":{"display_login":"Irtazaraza"}}