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

typos #44

Merged
merged 6 commits into from
May 29, 2024
Merged

typos #44

merged 6 commits into from
May 29, 2024

Conversation

ccoVeille
Copy link
Contributor

  • chore: fix typo in file name
  • chore: fix wrong comments and names
  • chore: fix Markdown fenced block identifiers
  • chore: fix typos
  • chore: fix invalid aliases for Morse decode
  • chore: fix acronyms case

@ccoVeille
Copy link
Contributor Author

Please find my reviews of your code

interacive => interactive
@ccoVeille ccoVeille force-pushed the typos branch 3 times, most recently from 8e0d0f8 to c52a2d5 Compare May 27, 2024 21:11
@abhimanyu003
Copy link
Owner

Hello @ccoVeille many thanks for your updates.
This looks great, but some test are failing, can you please fix them

@ccoVeille
Copy link
Contributor Author

Oh really? I will check when I would be in front of a computer. I'm on phone now

@ccoVeille
Copy link
Contributor Author

I'm a bit surprised this reported nothing 🤔

https://github.com/abhimanyu003/sttr/pull/44/checks

@ccoVeille
Copy link
Contributor Author

Could you tellme what is failing according to you? It would help me later when I'll be ankle to check

@abhimanyu003
Copy link
Owner

abhimanyu003 commented May 28, 2024

Please check this one. https://github.com/abhimanyu003/sttr/actions/runs/9260275381/job/25519173373?pr=44
Also you can run go test -v ./... locally. nothing major only few minor are failing.

--- FAIL: TestBase64Decode_Command (0.00s)
    base64_test.go:127: Description() = Decode your Base64 text, want Decode your base64 text
--- FAIL: TestBase64URLDecode_Command (0.00s)
    base64url_test.go:127: Description() = Decode your Base64 text with URL Safe, want Decode your base64 text with URL Safe
--- FAIL: TestSHA1Encode_Command (0.00s)
    crypto_test.go:136: Description() = Get the SHA-1 checksum of your text, want Get the SHA1 checksum of your text
    crypto_test.go:139: FilterValue() = SHA-1 Sum (sha1), want SHA1 Sum (sha1)
    crypto_test.go:148: Title() = SHA-1 Sum (sha1), want SHA1 Sum (sha1)
--- FAIL: TestSHA256Encode_Command (0.00s)
    crypto_test.go:217: Description() = Get the SHA-256 checksum of your text, want Get the SHA256 checksum of your text
    crypto_test.go:220: FilterValue() = SHA-256 Sum (sha256), want SHA256 Sum (sha256)
    crypto_test.go:229: Title() = SHA-256 Sum (sha256), want SHA256 Sum (sha256)
--- FAIL: TestSHA224Encode_Command (0.00s)
    crypto_test.go:298: Description() = Get the SHA-224 checksum of your text, want Get the SHA224 checksum of your text
    crypto_test.go:301: FilterValue() = SHA-224 Sum (sha224), want sha224 Sum (sha224)
    crypto_test.go:310: Title() = SHA-224 Sum (sha224), want sha224 Sum (sha224)
--- FAIL: TestSHA384Encode_Command (0.00s)
    crypto_test.go:379: Description() = Get the SHA-384 checksum of your text, want Get the SHA384 checksum of your text
    crypto_test.go:382: FilterValue() = SHA-384 Sum (sha384), want sha384 Sum (sha384)
    crypto_test.go:391: Title() = SHA-384 Sum (sha384), want sha384 Sum (sha384)
--- FAIL: TestSHA512Encode_Command (0.00s)
    crypto_test.go:460: Description() = Get the SHA-512 checksum of your text, want Get the SHA512 checksum of your text
    crypto_test.go:463: FilterValue() = SHA-512 Sum (sha-512), want SHA512 Sum (sha512)
    crypto_test.go:469: Name() = sha-512, want sha512
    crypto_test.go:472: Title() = SHA-512 Sum (sha-512), want SHA512 Sum (sha512)
--- FAIL: TestBcrypt_Command (0.00s)
    crypto_test.go:549: Description() = Get the bcrypt hash of your text, want Get the Bcrypt hash of your text
    crypto_test.go:552: FilterValue() = bcrypt Hash (bcrypt), want Bcrypt Hash (bcrypt)
    crypto_test.go:561: Title() = bcrypt Hash (bcrypt), want Bcrypt Hash (bcrypt)
--- FAIL: TestMSGPACKToJSON_Command (0.00s)
    json_test.go:254: FilterValue() = MSGPACK to JSON (msgpack-json), want MSGPACK To JSON (msgpack-json)
    json_test.go:263: Title() = MSGPACK to JSON (msgpack-json), want MSGPACK To JSON (msgpack-json)
FAIL
FAIL	github.com/abhimanyu003/sttr/processors	0.765s
FAIL

@ccoVeille
Copy link
Contributor Author

So strange, now github reports me the errors while it wasn't earlier. Did you change or trigger something?

Thanks anyway, it's clearer I will have a look when I can

@ccoVeille
Copy link
Contributor Author

pushed back

@ccoVeille
Copy link
Contributor Author

Im still unsure why the workflow is not triggered automatically

https://github.com/abhimanyu003/sttr/actions/runs/9289818782/usage

image

Does it mean you have to manually launch them ? if so, why is this set up like this?

@abhimanyu003
Copy link
Owner

Hello @ccoVeille
Thanks for your updates.
Github action didn't get triggered automatically because there is a setting that was enabled. Because of that, I have to approve your flow first.

Require approval for first-time contributors
Only first-time contributors will require approval to run workflows.

I have disabled it now. will review your PR and let you know :)

@abhimanyu003 abhimanyu003 merged commit 5aea98a into abhimanyu003:main May 29, 2024
2 checks passed
@abhimanyu003
Copy link
Owner

This is looking quite good to me. 👍 thanks so much 🙇‍♂️

@ccoVeille ccoVeille deleted the typos branch May 29, 2024 19:27
@ccoVeille
Copy link
Contributor Author

Hello @ccoVeille
Thanks for your updates.
Github action didn't get triggered automatically because there is a setting that was enabled. Because of that, I have to approve your flow first.

Require approval for first-time contributors
Only first-time contributors will require approval to run workflows.

I have disabled it now. will review your PR and let you know :)

Strange setting I have never faced until now. I learned something today 🤣

These are the few locations where `sttr` was highlighted, many thanks to all of you.
Please feel free to add any blogs/videos you may have made that discuss `sttr` to the list.
These are the few places where `sttr` got featured, many thanks to everyone.
If you have talked about `sttr` in your blog/video feel to add that to the list.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm doubtful about what happened here.

I didn't change these lines on purpose.

It looks like broken conflict resolution.

I'm sorry @abhimanyu003

Copy link
Owner

Choose a reason for hiding this comment

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

Yes, it looks like that. I will fix this. No worries on this. :)


* [Youtube: The Giants of Open Source - DevOps Paradox](https://youtu.be/4nFRKbY_HVE?t=2529?ref=abhimanyu003/sttr)
* [YouTube: The Giants of Open Source - DevOps Paradox](https://youtu.be/4nFRKbY_HVE?t=2529?ref=abhimanyu003/sttr)
* [Terminal Trove - Tool of the Week](https://terminaltrove.com/sttr/?ref=abhimanyu003/sttr)
* [nixCraft](https://www.cyberciti.biz/open-source/sttr-awesome-linux-unix-command-tool-for-transformation-string/?ref=abhimanyu003/sttr)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Same with these 2 lines that got added

@@ -36,6 +37,7 @@ func (p HTMLEncode) FilterValue() string {
return p.Title()
}

// HTMLEncode unescapes HTML to string
Copy link
Contributor Author

Choose a reason for hiding this comment

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

HTMLDecode here

Copy link
Owner

Choose a reason for hiding this comment

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

I'm going to push update for this.

ccoVeille added a commit to ccoveille-forks/abhimanyu003-sttr that referenced this pull request Jun 3, 2024
abhimanyu003 pushed a commit that referenced this pull request Jun 6, 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.

2 participants