-
Notifications
You must be signed in to change notification settings - Fork 197
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
ShortURL Plugins #1222
base: main
Are you sure you want to change the base?
ShortURL Plugins #1222
Conversation
Signed-off-by: Marcello Avila <[email protected]>
Signed-off-by: Marcello Avila <[email protected]>
Signed-off-by: Marcello Avila <[email protected]>
Signed-off-by: Marcello Avila <[email protected]>
Signed-off-by: Marcello Avila <[email protected]>
Signed-off-by: Marcello Avila <[email protected]>
Signed-off-by: Marcello Avila <[email protected]>
Signed-off-by: Marcello Avila <[email protected]>
Signed-off-by: Marcello Avila <[email protected]>
Signed-off-by: Marcello Avila <[email protected]>
Signed-off-by: Marcello Avila <[email protected]>
Unnecessary ChangesetsThe following package(s) are private and do not need a changeset:
Changed Packages
|
@avila-m-6 Do you think it would make sense to also support bringing your own short URL? I started a bit of work on this as well since it's an immediate need, but what I'm thinking is tying the route /shorturl to a path /go, then supporting the /go/:id I really like the simplicity of the creation at the top and the thoughtfulness to automatically copy it into the clipboard! |
I like the idea, but how about for a next iteration? So we get the ball rolling and some users validation. And I would like you to describe better that auth removal intent |
totally fair @avila-m-6 |
Ah yes, I like that. It makes sense as shorturl is no auth provider. Just a translator. It shouldn't ever have any sensitive data. I didn't add any authentication on the plugin though. That's on the backend integration step |
Signed-off-by: Marcello Avila <[email protected]>
* use discoverApi for api interaction * use configApi for url listing * validate url input format * refresh list on url creation across components * auto-copy to clipboard on creation * implement alertApi for verbosity * implement create and get apis * update backend api for creation values Signed-off-by: Marcello Avila <[email protected]>
Signed-off-by: Marcello Avila <[email protected]>
Signed-off-by: Marcello Avila <[email protected]>
Signed-off-by: Marcello Avila <[email protected]>
Only frontend tests are missing. But logic should be good to go |
Signed-off-by: Marcello Avila <[email protected]>
@BethGriggs, sorry to tag. I'm unclear on the next steps. Also I was instructed by the automation on #1220 that no changeset was required. But I saw a run that failed for a missing changeset? https://github.com/backstage/community-plugins/actions/runs/10917413204/job/30371450366#step:6:8 |
Signed-off-by: Marcello Ávila <[email protected]>
API report generation is failing in https://github.com/backstage/community-plugins/actions/runs/11020142480/job/30676982272?pr=1222 I do believe we should add changesets to trigger the release process. |
This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution! |
Signed-off-by: Marcello Avila <[email protected]>
…ns into shorturl-front
Signed-off-by: Marcello Avila <[email protected]>
…ns into shorturl-front
@BethGriggs, letting you know in case |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution @avila-m-6, left a few comments, nothing huge but should be looked at before we can merge this in.
Also, cna you please add yourself to the CODEOWNERS
file: https://github.com/backstage/community-plugins/blob/main/.github/CODEOWNERS
workspaces/shorturl/package.json
Outdated
"resolutions": { | ||
"@types/react": "^18", | ||
"@types/react-dom": "^18", | ||
"@microsoft/api-extractor": "7.36.4" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove this resolution, it's no longer needed. You'll also need to do a version bump to use the latest Backstage packages from 1.32.x
. Finally, this change will rename the API reports following a new naming convention so make sure to re-generate them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's still here 🤔
workspaces/shorturl/plugins/shorturl-backend/migrations/20230629144800_init.js
Show resolved
Hide resolved
Thanks for the contribution! |
Signed-off-by: Marcello Avila <[email protected]>
Signed-off-by: Marcello Avila <[email protected]>
Signed-off-by: Marcello Avila <[email protected]>
a69bc21
to
a7ccaed
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for resolving the comments @avila-m-6, just some simple adjustments to the config.d.ts
and getting the build green at which point we will be able to approve and merge this in.
workspaces/shorturl/package.json
Outdated
"resolutions": { | ||
"@types/react": "^18", | ||
"@types/react-dom": "^18", | ||
"@microsoft/api-extractor": "7.36.4" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's still here 🤔
Signed-off-by: Marcello Avila <[email protected]>
I took a good read at the api reports resources but I don't understand why they still came as I did the v1.32 bump after removing the resolution. I read through backstage/backstage#25671 and #886 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like there's still issues with the API Reports.
@@ -0,0 +1 @@ | |||
{ "version": "1.30.0" } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This tells me you are still on an older version which is probably why the API Reports are not coming up correctly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should be able to run yarn backstage-cli versions:bump --release main
from the root of your workspace: '/workspaces/shorturl
. Then commit those changes. Once that's done then try building the API Reports again with yarn build:api-reports
Hey, I just made a Pull Request!
This is the set of ShortURL plugins, both frontend and backend sharing workspace.
This plugin will enable the creation of short urls within
/shorturl
and redirection through/go:id
.Features:
HOST/go/:id
✔️ Checklist
Signed-off-by
line in the message. (more info)Redirect page has a progress bar for loading, and an error panel for failures:
This is WIP. Next steps:
backstage.com/go/AAABBB
This is related to #221 and #1220