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

Added support to view the Encoding history for MVS and USS in the History View #2776

Merged
merged 8 commits into from
Mar 22, 2024

Conversation

KaranP25
Copy link
Contributor

@KaranP25 KaranP25 commented Mar 12, 2024

Proposed changes

Release Notes

Milestone:

Changelog: Added support to view the Encoding history for MVS and Dataset in the History View.

Types of changes

What types of changes does your code introduce to Zowe Explorer?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Updates to Documentation or Tests (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This checklist will be used as reference for both the contributor and the reviewer

  • I have read the CONTRIBUTOR GUIDANCE wiki
  • PR title follows Conventional Commits Guidelines
  • PR Description is included
  • gif or screenshot is included if visual changes are made
  • yarn workspace vscode-extension-for-zowe vscode:prepublish has been executed
  • All checks have passed (DCO, Jenkins and Code Coverage)
  • I have added unit test and it is passing
  • I have added integration test and it is passing
  • There is coverage for the code that I have added
  • I have tested it manually and there are no regressions found
  • I have added necessary documentation (if appropriate)
  • Any PR dependencies have been merged and published (if appropriate)

Further comments

Signed-off-by: Karan Patel <17771013+KaranP25@users.noreply.github.com>
@rudyflores rudyflores self-requested a review March 12, 2024 18:24
@zFernand0 zFernand0 self-requested a review March 12, 2024 20:07
Signed-off-by: Rudy Flores <68666202+rudyflores@users.noreply.github.com>
@rudyflores rudyflores changed the title Draft PR to check test Add encodingHistory to PersistentSchema and HistoryView Mar 12, 2024
Copy link

codecov bot commented Mar 12, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.27%. Comparing base (206bf06) to head (625f36f).

Additional details and impacted files
@@           Coverage Diff            @@
##             main    #2776    +/-   ##
========================================
  Coverage   93.26%   93.27%            
========================================
  Files         102      102            
  Lines       10604    10618    +14     
  Branches     2202     2304   +102     
========================================
+ Hits         9890     9904    +14     
  Misses        713      713            
  Partials        1        1            

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@KaranP25 KaranP25 changed the title Add encodingHistory to PersistentSchema and HistoryView Added support to view the Encoding history for MVS and USS in the History View Mar 19, 2024
… History View

Signed-off-by: Karan <karan@Karans-MacBook-Pro-2.local>
@KaranP25 KaranP25 marked this pull request as ready for review March 19, 2024 21:09
Copy link
Member

@zFernand0 zFernand0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes LGTM! 😋
Left a few small requests/comments 🥳

@rudyflores
Copy link
Contributor

@zFernand0 I see the changelog check failing, even though the changelog seems to be in place in this PR. Do you know if this is a known issue for the check to break when changes are made specifically to our webview code?

@zFernand0
Copy link
Member

zFernand0 commented Mar 20, 2024

zFernand0 I see the changelog check failing, even though the changelog seems to be in place in this PR. Do you know if this is a known issue for the check to break when changes are made specifically to our webview code?

I kind of agree that it probably doesn't need to be looking for that since it's a private package. We can let this PR just have that failing check, or add the no-changelog label so that it doesn't look for changelog-updates in new commits.

Ideally, we would enhance the checklog checker to have a flag/setting that doesn't look for changelog updates in private packages of a monorepo 😋

The issue below should help us not to forget about this:

Copy link
Contributor

@rudyflores rudyflores left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for making this change, left some comments regarding some potential edits to the code changes

Signed-off-by: Karan <karan@Karans-MacBook-Pro-2.local>
@KaranP25
Copy link
Contributor Author

Thank you @zFernand0 and @rudyflores for your comments, I have now addressed them with my latest commit. Feel free to take a look and comment on anything else I might have missed.

JillieBeanSim
JillieBeanSim previously approved these changes Mar 21, 2024
Copy link
Contributor

@JillieBeanSim JillieBeanSim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! thanks @KaranP25 for this added functionality in the edit history GUI

Signed-off-by: Karan <karan@karans-mbp-2.war.can.ibm.com>
zFernand0
zFernand0 previously approved these changes Mar 21, 2024
Copy link
Member

@zFernand0 zFernand0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 😋
Functionality works great too! 🥳

Random question:
Are we concerned that MVS and USS share the same encoding-history?

I don't think it has been a problem so far, but with this enhancement we are giving more visibility to this information.

I'm just wondering if people will find it odd that deleting an encodingHistory item on MVS also deletes it for USS 😋

packages/zowe-explorer/src/shared/utils.ts Show resolved Hide resolved
@zFernand0 zFernand0 requested a review from JillieBeanSim March 21, 2024 14:41
… to the localstorage

Signed-off-by: Karan <karan@karans-mbp-2.war.can.ibm.com>
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
26.0% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud

@zFernand0
Copy link
Member

zFernand0 I believe from what we discussed with @t1m0thyj on this setting is that we wanted them to share this setting between MVS and USS, did this change?
I originally intended for these to be independent but it seemed that we wanted to maintain them as shared between each other 🤔

Thanks for sharing! 🥳
I partially remember some of those discussions. My apologies for questioning the current implementation.
Since that's what was decided, then I'm onboard 😋
Thanks for the reminder... 🥳

Copy link
Contributor

@rudyflores rudyflores left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Screenshot 2024-03-21 at 4 51 48 PM

Looks good to me, I did see an issue related to clicking on Encoding History in the drop down and then clicking sessions and the dropdown resizing its size which can be a little odd with all the resizing going on for the user, so we may want to work on keeping the dropdown length consistent in a follow up PR

@zFernand0 zFernand0 merged commit 0ddb5d9 into zowe:main Mar 22, 2024
16 of 19 checks passed
@JillieBeanSim JillieBeanSim added this to the v2.16.0 milestone Mar 27, 2024
rudyflores added a commit that referenced this pull request Jun 21, 2024
Signed-off-by: Rudy Flores <68666202+rudyflores@users.noreply.github.com>
t1m0thyj added a commit that referenced this pull request Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants