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.

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

feat: company naming logic in portal #1454

Conversation

Usmanfee
Copy link
Contributor

@Usmanfee Usmanfee commented Jan 29, 2025

Description

Replaced different kinds of identifiers for the company (e.g., Name, hostCompanyName, and customer) with LegalName and short LegalName.

Changelog entry
- **Updated Naming logic**
  -Replaced companies name with legal identifiers [#1452](https://github.com/eclipse-tractusx/portal-frontend/issues/1452)

Why

Due to business requirements, the portal needs to display the short LegalName for businesses along with the LegalName. Some businesses might have longer names, so instead of the full name, we want to display the short LegalName.

Issue

#1452

Dependency

BE needs to implement these respective changes on their side as well and then we will be able to test it.
related shared-component issue: eclipse-tractusx/portal-shared-components#422
shared-component PR: eclipse-tractusx/portal-shared-components#423

Checklist

  • I have performed a self-review of my own code
  • I have successfully tested my changes locally

@Usmanfee Usmanfee changed the title feat: legalName update logic in portal feat: company naming logic in portal Jan 30, 2025
@saadanzari
Copy link
Member

@Usmanfee dependencies error here

@typecastcloud
Copy link
Contributor

typecastcloud commented Jan 30, 2025

@Usmanfee
Replacing attribute names of existing endpoints is not the way to go here. Old long name attribute should also stay as fallback to not disrupt anything. Looks like a huge amount of endpoint changes.
Please discuss in the issue with all relevant parties on how this should be implemented. This needs to go back to the drawing board imho. :(

CC: @ybidois

@Usmanfee
Copy link
Contributor Author

Usmanfee commented Jan 30, 2025

Thanks @typecastcloud for the sneak peak.
I talked to @tfjanjua about it and listed all the api where the mentioned changed of FE expects new values and these value must be the part of response but you also make sense when it comes to fallback solution.
As for the relevant parties, most of the changes on the BE side will be made directly in the code rather than in any third-party service endpoint. I will check again by tomorrow!
CC @ybidois @dhiren-singh-007

@Usmanfee Usmanfee marked this pull request as ready for review January 31, 2025 08:44
@Usmanfee Usmanfee closed this Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: USER READY
Development

Successfully merging this pull request may close these issues.

3 participants