Copy button not visible if the key is too long

[harshsbhat]

Preliminary Checks

• I have reviewed the documentation: https://unkey.com/docs

• I have searched for existing issues: https://github.com/unkeyed/unkey/issues

• This issue is not a question, general help request, or anything other than a bug report directly related to Unkey. Please ask questions in our Discord community: https://unkey.com/discord.

Reproduction / Replay Link (Optional)

No response

Issue Summary

After creating a key longer than 87 bytes, the copy button is not visible near the key.

Steps to Reproduce

1. Go to https://app.unkey.com/apis/[api_123]/keys/[ks_123]/new
2. Create a new key with byte size 87 or more.
3. Notice that copy button is not visible

Expected behavior

The copy and eye buttons should be visible regardless of the key size.

Other information

No response

Screenshots

Version info

- OS:
- Node:
- npm:

[linear]

ENG-1458 Copy button not visible if the key is too long

[harshsbhat]

Eye button is visible at 87 but increase the key size more and it won't be visible too

[mitullakkad]

/assign

[oss-gg]

This issue is not part of oss.gg hackathon. Please pick a different one or start with a side quest

[0xJaskeerat]

Hey @perkinsjr @chronark
Please review this issue , I guess this is valid issue
please add the oss.gg label and I would love to contribute to it on firsthand
You can assign it to me

[FaheemOnHub]

/assign

[oss-gg]

This issue is not part of oss.gg hackathon. Please pick a different one or start with a side quest

[FaheemOnHub]

@harshsbhat kindly assign me this issue

[FaheemOnHub]

@harshsbhat also add hacktoberfest label and please assign me, that would be great

[harshsbhat]

@FaheemOnHub I am NOT the maintainer of this repo

[Desktoo]

/assign

[oss-gg]

This issue is not part of oss.gg hackathon. Please pick a different one or start with a side quest

[hacanand]

/assign

[oss-gg]

This issue is not part of oss.gg hackathon. Please pick a different one or start with a side quest

[chronark]

/award 50

[oss-gg]

Awarding harshsbhat: 50 points 🕹️ Well done! Check out your new contribution on oss.gg/harshsbhat

[oss-gg]

You already have an open issue assigned to you here. Once that's closed or unassigned, only then we recommend you to take up more.

[kumawatvaibhav]

/assign

[oss-gg]

Assigned to @kumawatvaibhav! Please open a draft PR linking this issue within 48h ⚠️ If we can't detect a PR from you linking this issue in 48h, you'll be unassigned automatically 🕹️ Excited to have you ship this 🚀

[oss-gg]

@kumawatvaibhav, please open a draft PR linking this issue within 12 hours. If we can't detect a PR in 12 hours, you will be unassigned automatically.

[oss-gg]

@kumawatvaibhav has not opened a PR for this issue within 48 hours. They have been unassigned from the issue; anyone can now take it up.

[adot-7]

/assign

[oss-gg]

Assigned to @akash-2004! Please open a draft PR linking this issue within 48h ⚠️ If we can't detect a PR from you linking this issue in 48h, you'll be unassigned automatically 🕹️ Excited to have you ship this 🚀

[adot-7]

I have fixed this issue, it would be helpful if maintainers review it so that I can work on another open issue

[adot-7]

/assign

[oss-gg]

This issue is already assigned to you. Let's get this shipped!

[oss-gg]

@akash-2004, please open a draft PR linking this issue within 12 hours. If we can't detect a PR in 12 hours, you will be unassigned automatically.

[oss-gg]

@akash-2004 has not opened a PR for this issue within 48 hours. They have been unassigned from the issue; anyone can now take it up.

[adot-7]

/assign

[oss-gg]

This issue is already assigned to you. Let's get this shipped!