fix(backend): use new backend for orgdiagram for valid results

[paule96]

No description provided.

[paule96]

@mschwrdtnr this is more or less a big restyle. :D so maybe the label was good. The result of the restyle is that the bug is fixed yes, but the big thing is that we use the new backend for the organigram. So can I add the label again? :P

[DanielHabenicht]

Why did this not trigger any build?

[paule96]

It does?

[mmsgithub-ci]

Preview Environment ready at https://pr-664.demo-phonebook.me

[mschwrdtnr]

@mschwrdtnr this is more or less a big restyle. :D so maybe the label was good. The result of the restyle is that the bug is fixed yes, but the big thing is that we use the new backend for the organigram. So can I add the label again? :P

For me restyled means something different and also your title says "fix" 🤔

[paule96]

Yes because I can't use both. Or can I? Can I do something like: fix(something) feature(something)

So restyle only includes formating?

[mschwrdtnr]

Yes because I can't use both. Or can I? Can I do something like: fix(something) feature(something)

So restyle only includes formating?

I don't make the rules^^ We should agree on something and write it in our "Contribution Guidelines" @ #412

If it's really just an restyle thing you can use style( ), but I think this is more than style, so maybe chore. Semantic Release is using the Angular commit guidelines

[DanielHabenicht]

Yes because I can't use both. Or can I? Can I do something like: fix(something) feature(something)

So restyle only includes formating?

why should it be both?
It should be either a fix or a new feature. If it is both it should be two different commits.
restyle on restyles the code. It does not change the functionality.

[DanielHabenicht]

ready to merge? @paule96

[mmsgithub-ci]

Preview Environment ready at https://pr-664.demo-phonebook.me

error in backend

[DanielHabenicht]

Your backend seems to have an error for development

[paule96]

Your backend seems to have an error for development

have you an url for me?

[DanielHabenicht]

/azp run T-Systems-MMS.phonebook-preview

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mmsgithub-ci]

Preview Environment ready at https://pr-664.demo-phonebook.me

[DanielHabenicht]

@paule96 https://pr-664.demo-phonebook.me/api/OrgUnit

[mmsgithub-ci]

Preview Environment ready at https://pr-664.demo-phonebook.me

[paule96]

lol don't has the problem local... what is different in the demo...

[mmsgithub-ci]

Preview Environment ready at https://pr-664.demo-phonebook.me

[mmsgithub-ci]

🎉 This PR is included in version 1.43.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀