Component update#539
Conversation
Signed-off-by: Julia Yan <julia.yan@ibm.com>
Signed-off-by: Julia Yan <julia.yan@ibm.com>
Signed-off-by: Julia Yan <julia.yan@ibm.com>
Signed-off-by: Julia Yan <julia.yan@ibm.com>
|
Putting in draft until v3.0.0 is out |
|
We should make a note to remove the Mapepire Component from this extension and use the core's now. |
|
👋 A new build is available for this PR based on b60c26f. |
Signed-off-by: Seb Julliand <sebjulliand@gmail.com>
Signed-off-by: Seb Julliand <sebjulliand@gmail.com>
Signed-off-by: Seb Julliand <sebjulliand@gmail.com>
Signed-off-by: Seb Julliand <sebjulliand@gmail.com>
SanjulaGanepola
left a comment
There was a problem hiding this comment.
Okay, I tried to do hopefully a thorough review of this (lots of changes!) and commented anything and everything I found 😅
Just wanted to point out that it looks like there are a whole lot of type errors still in several files. Are these unrelated to the changes made in this branch? Also not sure why these are not flagged by the build.
| .addSelect(`database name`, `Database name`, [ | ||
| {text: `System Base`, description: `*SYSBAS`, value: ``, selected: options["database name"] === ``}, | ||
| ...Object.values(connection.getAllIAsps()).map(asp => ({text: asp.name, description: asp.name, value: asp.rdbName, selected: options["database name"] === asp.rdbName})) | ||
| ], formatDescription(dbNameText)) |
There was a problem hiding this comment.
Why do we no longer fetch this and instead rely on the user to set it? From what I see in Code4i, this API is still available.
Is this related to #546 which was just opened? In which case, lets link that issue to this PR too.
There was a problem hiding this comment.
That's been removed from the API. The ASP_INFO service that gave us this info cannot be run by any user in 7.6. So listing ASP is not possible anymore, hence the switch to a simple input here.
There was a problem hiding this comment.
Oh didn't know that. Is there any alternatives we can use to still fetch this @forstie? Or input box the way to go?
|
@forstie After the comments I just left are addressed, it would be great if you could test this out as well just to make sure nothing was broken. |
|
I'm ready to test it when given the go ahead. |
Signed-off-by: Seb Julliand <sebjulliand@gmail.com>
|
@SanjulaGanepola I tried to fix most of the type errors. It must be ok now (I put //@ts-ignore on some of them because these cases would need more changes). |
Co-authored-by: Sanjula Ganepola <32170854+SanjulaGanepola@users.noreply.github.com>
Co-authored-by: Sanjula Ganepola <32170854+SanjulaGanepola@users.noreply.github.com>
Co-authored-by: Sanjula Ganepola <32170854+SanjulaGanepola@users.noreply.github.com>
Co-authored-by: Sanjula Ganepola <32170854+SanjulaGanepola@users.noreply.github.com>
Co-authored-by: Sanjula Ganepola <32170854+SanjulaGanepola@users.noreply.github.com>
|
@sebjulliand Sounds good, let me know when this is ready for a re-review :) |
Signed-off-by: Julia Yan <julia.yan@ibm.com>
|
@SanjulaGanepola resolved the two comments for the components |
Signed-off-by: Seb Julliand <sebjulliand@gmail.com>
@forstie For testing, this PR doesn't actually have any changes that actually impact functionality. Rather we are no longer installing and have our own mapepire logic in this extension, and instead re-using similar mapepire logic which was added in Code for IBM i. > 3.0.0. However, since this PR does touch a lot of files though, I just tested everything more generally to make sure nothing was broken. I am hoping you can help do the same. Note: Content assist is not working properly right now, but everything else seems to be good. I have a comment above for that. Note the VSIX can be found here: #539 (comment) |
Signed-off-by: Seb Julliand <sebjulliand@gmail.com>
Signed-off-by: Seb Julliand <sebjulliand@gmail.com>
Signed-off-by: Seb Julliand <sebjulliand@gmail.com>
|
@SanjulaGanepola I fixed those types issue and the completion (hopefully). |
SanjulaGanepola
left a comment
There was a problem hiding this comment.
Awesome, all looks good on my end
forstie
left a comment
There was a problem hiding this comment.
I'll test post release.


Update to match the component checking in base extension v3.0.0