umputun/remark42

Lack of auth providers doesn't show errors in the UI

Open

#1456 opened on Jul 31, 2022

View on GitHub
 (10 comments) (0 reactions) (0 assignees)Go (5,500 stars) (432 forks)user submission
bugfrontendhelp wanted

Description

Here is what one would see by running Remark42 like ./remark42.darwin-arm64 server --secret=12345 --url=http://127.0.0.1:8080 :

Let's name it "Read-only mode" and write some helping text like "No authentication methods are set up, the comments are in the read-only mode".

Contributor guide

Tech stack
goreact
Domain
frontendbackend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
GoReact
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
The issue requests adding a 'Read only mode' message when no authentication providers are configured. The change likely involves modifying the UI to check for auth provider availability. Look for React components that render the comment area (e.g., in frontend/apps/remark42) and a backend endpoint or state that indicates auth config. Consider adding a conditional render based on a prop or API response. No linked PRs or assignees, so this is available.