Skip to content

Conversation

@sergiolms
Copy link
Contributor

Description

Resolves #3529

Here's what an error looks like now:

Captura de pantalla 2024-10-11 a las 14 09 02

Checklist

  • I have followed the guidelines in the Contributing document
  • My changes follow the coding style of this project
  • My changes build without any errors or warnings
  • My changes have been formatted and linted
  • My changes include any required corresponding changes to the documentation (including CHANGELOG.md and README.md)
  • My changes have been rebased and squashed to the minimal number (typically 1) of relevant commits
  • My changes have a descriptive commit message with a short title, including a Fixes $XXX - or Closes #XXX - prefix to auto-close the issue that your PR addresses

@sergiolms sergiolms self-assigned this Oct 11, 2024
Copy link
Contributor

@axosoft-ramint axosoft-ramint left a comment

Choose a reason for hiding this comment

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

A couple of thoughts I wanted to get your input on before testing

@sergiolms sergiolms force-pushed the feature/#3529_change_tag_terminal-run_cmds_into_normal_cmds branch from 4c79fc8 to 514f618 Compare October 15, 2024 14:20
@axosoft-ramint axosoft-ramint self-requested a review October 15, 2024 14:59
Copy link
Contributor

@axosoft-ramint axosoft-ramint left a comment

Choose a reason for hiding this comment

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

Build errors:

image

I think most of them are solvable by setting up a type on tagErrorAndReason: const tagErrorAndReason: [RegExp, TagErrorReason][] = ...

Not sure on that last one though.

@sergiolms
Copy link
Contributor Author

@axosoft-ramint

I think most of them are solvable by setting up a type on tagErrorAndReason: const tagErrorAndReason: [RegExp, TagErrorReason][] = ...

Yup... That was mostly it. I'm not sure why it didn't pop up before. 🤷‍♂️ Thank you

@sergiolms sergiolms force-pushed the feature/#3529_change_tag_terminal-run_cmds_into_normal_cmds branch from 59925a0 to 3597a47 Compare October 23, 2024 10:46
@sergiolms sergiolms force-pushed the feature/#3529_change_tag_terminal-run_cmds_into_normal_cmds branch from 3597a47 to 4afddec Compare October 23, 2024 12:50
Copy link
Contributor

@axosoft-ramint axosoft-ramint left a comment

Choose a reason for hiding this comment

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

Tested creating and deleting a tag and it LGTM. Let me know if you want me to test other cases.

@sergiolms sergiolms force-pushed the feature/#3529_change_tag_terminal-run_cmds_into_normal_cmds branch from 4afddec to e7aab45 Compare November 7, 2024 13:35
@axosoft-ramint axosoft-ramint merged commit 0a71aa6 into main Nov 7, 2024
3 checks passed
@axosoft-ramint axosoft-ramint deleted the feature/#3529_change_tag_terminal-run_cmds_into_normal_cmds branch November 7, 2024 18:40
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.

Change tag terminal-run commands into normal commands w/ proper error handling

3 participants