Skip to content

Conversation

@paleloser
Copy link
Collaborator

@paleloser paleloser commented Aug 20, 2025

This is a proposal to satisfy the discussion started here: #48.

The navigation is enabled without authentication required. However, when the user reaches the point where authentication is necessary, the actionable cards/buttons are disabled with a tooltip:

image image

Once the user goes to Settings and configures valid credentials, these actions are enabled.

@paleloser paleloser added the enhancement Feature improvement label Aug 20, 2025
@paleloser paleloser marked this pull request as ready for review August 25, 2025 09:24
@paleloser paleloser requested a review from a team as a code owner August 25, 2025 09:24
Copy link
Contributor

@andresbono andresbono left a comment

Choose a reason for hiding this comment

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

When building the container image, tsc raised a few errors: error TS7006: Parameter 'XXXXX' implicitly has an 'any' type. I updated the compilation settings to bypass, but maybe we should look into those errors

}
}

const AuthnWrapper = ({ children } : { children: ReactElement }) => disabled ? <Tooltip title='Log in to install this application'>{ children }</Tooltip> : <>{ children }</>
Copy link
Contributor

Choose a reason for hiding this comment

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

Since you are not prompted directly to the login form, does it make sense to complete a little bit how to do so?

Suggested change
const AuthnWrapper = ({ children } : { children: ReactElement }) => disabled ? <Tooltip title='Log in to install this application'>{ children }</Tooltip> : <>{ children }</>
const AuthnWrapper = ({ children } : { children: ReactElement }) => disabled ? <Tooltip title='Go to the extension settings and log in to install this application'>{ children }</Tooltip> : <>{ children }</>

Copy link
Contributor

Choose a reason for hiding this comment

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

Would it make sense to invite the user to login via notifications?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Definitely, I've pushed 7af2c24 so the initial notification encourages the users to log in.

@paleloser
Copy link
Collaborator Author

When building the container image, tsc raised a few errors: error TS7006: Parameter 'XXXXX' implicitly has an 'any' type. I updated the compilation settings to bypass, but maybe we should look into those errors

@andresbono I'd say that's related to the autogenerated backend clients. Try running npm run generate-backend-client and then npm run build.

@andresbono
Copy link
Contributor

When building the container image, tsc raised a few errors: error TS7006: Parameter 'XXXXX' implicitly has an 'any' type. I updated the compilation settings to bypass, but maybe we should look into those errors

@andresbono I'd say that's related to the autogenerated backend clients. Try running npm run generate-backend-client and then npm run build.

Thank you. A rebase from main made the trick in the end.

type Auth = string | null | undefined

type ReducerAction = {
type: 'set' | 'update' | 'delete' | 'dismiss_errors',
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Unrelated, but this was unused

Copy link
Contributor

@andresbono andresbono left a comment

Choose a reason for hiding this comment

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

LGTM

@paleloser paleloser merged commit 204552e into main Oct 21, 2025
5 checks passed
@paleloser paleloser deleted the display-collection-without-loggin-in branch October 21, 2025 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement Feature improvement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants