Skip to content

Conversation

sahiljagtap08
Copy link

@sahiljagtap08 sahiljagtap08 commented Oct 16, 2025

Contributor checklist

  • This pull request is on a separate branch and not the main branch
  • I have tested my code with the ./gradlew lintKotlin detekt test command as directed in the testing section of the contributing guide

Description

The information icon was appearing in both idle state (command selection) and invalid state (after invalid input). This fix ensures the icon only appears when there's actually an invalid input error, not during normal command browsing.

Changes:

  • Added binding.ivInfo.visibility = View.GONE in setupIdleView()

  • Icon now only shows in setupInvalidView() as intended

    The Problem:

    • Icon was showing when users clicked the Scribe key and selected a command (confusing for new users)
    • Icon was correctly showing for invalid input (this behavior is kept)

    The Solution:
    Added binding.ivInfo.visibility = View.GONE in three locations:

    • setupIdleView() - hides icon in normal typing state
    • setupSelectCommandView() - hides icon when viewing command menu
    • setupToolbarView() - hides icon when a command is selected

    The icon now only shows in setupInvalidView() when there's actually invalid input.

    Testing:

    • Tested that icon doesn't appear when selecting commands from menu
    • Tested that icon properly appears when entering invalid text like "asdfghjkl;"
    • Verified icon click functionality still works in invalid state

    Related issue

…ribe-org#497)

The information icon was appearing in idle state, SELECT_COMMAND state,
and when selecting specific commands (TRANSLATE, CONJUGATE, PLURAL).
This fix ensures the icon only appears when there's an invalid input error.

Changes:
- Added binding.ivInfo.visibility = View.GONE in setupIdleView()
- Added binding.ivInfo.visibility = View.GONE in setupSelectCommandView()
- Added binding.ivInfo.visibility = View.GONE in setupToolbarView()
- Icon now only shows in setupInvalidView() as intended
Copy link

Thank you for the pull request! ❤️

The Scribe-Android team will do our best to address your contribution as soon as we can. If you're not already a member of our public Matrix community, please consider joining! We'd suggest that you use the Element client as well as Element X for a mobile app, and definitely join the General and Android rooms once you're in. Also consider attending our bi-weekly Saturday dev syncs. It'd be great to meet you 😊

Copy link

Maintainer Checklist

The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

  • The linting, formatting and testing workflows within the PR checks do not indicate new errors in the files changed

    • Tests may need to be reran as they're at times not deterministic
  • The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

First PR Commit Check

  • The commit messages for the remote branch should be checked to make sure the contributor's email is set up correctly so that they receive credit for their contribution
    - The contributor's name and icon in remote commits should be the same as what appears in the PR
    - If there's a mismatch, the contributor needs to make sure that the email they use for GitHub matches what they have for git config user.email in their local Scribe-Android repo (can be set with git config --global user.email "GITHUB_EMAIL")

@andrewtavis andrewtavis added the hacktoberfest-accepted Accepted as a part of Hacktoberfest label Oct 18, 2025
@andrewtavis
Copy link
Member

Hey @sahiljagtap08 👋 In checking the commit message for this PR, it looks like your email for GitHub isn't set up properly. Can you make sure that the email you use for GitHub matches what you have for git config user.email in your local Scribe-Android repo (can be set with git config --global user.email "GITHUB_EMAIL"). As it stands, you wouldn't get a contribution to your account for this PR 😊 Could you fix your email, send a commit to this with a random change, and then send another commit to remove the change? I can then squash the changes and your account will get the commit.

If it's not important to you, then we can also proceed with the review! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hacktoberfest-accepted Accepted as a part of Hacktoberfest

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants