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

Add tagging func to a resource for a specific revision #1425

Merged
merged 5 commits into from
Nov 1, 2023

Conversation

bilalesi
Copy link
Contributor

Allow the user to tag a resource for a specific revision

Description

Screenshot 2023-10-30 at 16 28 52 Screenshot 2023-10-30 at 16 29 21

How has this been tested?

Types of changes

  • Bug fix (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)

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added necessary unit and integration tests.
  • I have added screenshots (if applicable), in the comment section.

@bilalesi bilalesi requested a review from Dinika October 30, 2023 15:29
@bilalesi bilalesi self-assigned this Oct 30, 2023
Copy link
Contributor

@Dinika Dinika left a comment

Choose a reason for hiding this comment

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

Code-wise good to me - I've left two comments that are not mandatory. I'll test it now.

},
{
pattern: /^[a-zA-Z0-9_-]+$/,
message: 'Tag must contains only letters and numbers',
Copy link
Contributor

Choose a reason for hiding this comment

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

Two things:

  1. Just double checking, are dashes really allowed by delta? I thought it was only alpha-numeric characters or underscore. I may be misrembering though.

  2. The message says that only letters and numbers are allowed. Maybe we should also add that dashes and underscores are also allowed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

  1. Simon has mentioned that the orgs name and tags should have the same regex (may be we forget to mention the _ and -)
  2. you're right message updated.

src/shared/containers/ResourceViewActionsContainer.tsx Outdated Show resolved Hide resolved
@codecov-commenter
Copy link

codecov-commenter commented Nov 1, 2023

Codecov Report

Attention: 24 lines in your changes are missing coverage. Please review.

Comparison is base (39dd257) 49.65% compared to head (72239c9) 47.99%.
Report is 89 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1425      +/-   ##
===========================================
- Coverage    49.65%   47.99%   -1.66%     
===========================================
  Files          249      249              
  Lines        11339    11362      +23     
  Branches      2652     2655       +3     
===========================================
- Hits          5630     5453     -177     
- Misses        5673     5876     +203     
+ Partials        36       33       -3     
Files Coverage Δ
src/shared/components/History/index.tsx 40.00% <0.00%> (-4.45%) ⬇️
src/shared/containers/HistoryContainer.tsx 30.00% <25.00%> (-2.00%) ⬇️
...shared/containers/ResourceViewActionsContainer.tsx 10.95% <11.76%> (-43.66%) ⬇️

... and 8 files with indirect coverage changes

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

@bilalesi bilalesi merged commit 36de6be into develop Nov 1, 2023
1 check passed
@bilalesi bilalesi deleted the feature-4011/allow-resource-tagging branch November 1, 2023 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants