v0.45.1 support for /ununifi/cdp and /unifi/cdp/create

[taiki1frsh]

The problem was the change of the type that is created by ununifi-client automatically.

Specifically, IParams became to have two array objects which are collateral_params and debt_params. But, the code wasn't applied to these change.

So, we made principalDebtParam variable to compromise with pages/create/create component com in project/telescope-extension/src/app/utils/function.ts.

[taiki1frsh]

After some more revision of the other component to make build pass, I tried to create a CDP with type ubtc-jpy-3-2.

But, the same issue that we (me and @YasunoriMATSUOKA ) had occurred.
So, I look into this component again.

[YasunoriMATSUOKA]

@taikiFurusyo
Thank you for your reporting. Please continue to investigate them again.

Well, I concern that the reason CI is failing is because the changes to package-lock.json have not been committed. Please execute npm i again and commit the changes to package-lock.json, just to be sure.

[taiki1frsh]

Oh, thanks for the precise advise.
In local, the build failed with the branch feat/v0.45.1-cdp's issue anyway, but it is so helpful.

[Senna46]

ff3e998
The contents of ununifi.cdp.IParams retrieved are now compatible with v0.45.1.
But, the number of parameters that can be retrieved has changed from one to two, and the display is now corrupted. This will be corrected as well.

[YasunoriMATSUOKA]

@Senna46
OK. Thank you.

[Senna46]

@YasunoriMATSUOKA
I think the build will go through without problems.
Please review /ununifi/cdp and /unifi/cdp/create, if you have no problems.

Changes

The display of CDP parameters is changed.

• The part that used to be Other Status is now included in Debt Params, so it is displayed according to Debt Params.
• The display of the parameters in *ngFor, which was not beautiful, has been improved by displaying the type for Collateral Params and the denom for Debt Params outside the card.]

[YasunoriMATSUOKA]

@Senna46
Can you create cdp with this PR implementation?

[Senna46]

Untested. is it ok to check with ununifi-8-private-test?

[YasunoriMATSUOKA]

Yes. Plz check with ununifi-8-private-test.

[Senna46]

@YasunoriMATSUOKA CC: @taikiFurusyo
After some modifications to the code, CDP creation is now possible.
The CDP has been created as shown in the second photo.

On the other hand, there is a problem that it does not appear in /cdp/cdps.
I will continue working on this, but if you are in a hurry, you can merge this and deal with it in another Pull Request.

[YasunoriMATSUOKA]

@Senna46
Thank you for your fix!
But, on the following screenshot, created cdp should be shown in the list, but it is not shown in the list.
Can you fix that?

[Senna46]

@YasunoriMATSUOKA
As mentioned above, this will be a /cdp/cdps problem, should this Pull Request solve the problem?
I will proceed with the work.

[YasunoriMATSUOKA]

@Senna46
Thank you for your comment.
Sorry, I missed your comment.
Let's merge it once and fix it in the next PR.

[YasunoriMATSUOKA]