Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

not get any warning

See original GitHub issue

I installed the library according to the instructions But I do not get any warning about TouchableOpacity

What should I do?

eslintrc.js

module.exports = {
  root: true,
  extends: ['@react-native-community', 'plugin:react-native-a11y/ios'],
};

package.json

{
  "name": "reduxTs",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "start": "react-native start",
    "test": "jest",
    "lint": "eslint . --ext .js,.jsx,.ts,.tsx"
  },
  "dependencies": {
    "@reduxjs/toolkit": "^1.5.0",
    "react": "16.13.1",
    "react-native": "0.63.4",
    "react-native-fingerprint-scanner": "^6.0.0",
    "react-native-touch-id": "^4.4.1",
    "react-redux": "^7.2.2",
    "redux-thunk": "^2.3.0"
  },
  "devDependencies": {
    "@babel/core": "^7.8.4",
    "@babel/runtime": "^7.8.4",
    "@react-native-community/eslint-config": "^1.1.0",
    "@types/jest": "^25.2.3",
    "@types/react-native": "^0.63.2",
    "@types/react-redux": "^7.1.16",
    "@types/react-test-renderer": "^16.9.2",
    "babel-jest": "^25.1.0",
    "babel-plugin-module-resolver": "^4.1.0",
    "eslint": "^7.20.0",
    "eslint-config-airbnb": "^18.2.1",
    "eslint-config-prettier": "^7.2.0",
    "eslint-plugin-import": "^2.22.1",
    "eslint-plugin-jsx-a11y": "^6.4.1",
    "eslint-plugin-prettier": "^3.3.1",
    "eslint-plugin-react": "^7.22.0",
    "eslint-plugin-react-native-a11y": "^2.0.4",
    "jest": "^25.1.0",
    "metro-react-native-babel-preset": "^0.59.0",
    "prettier": "^2.2.1",
    "react-test-renderer": "16.13.1",
    "typesafe-actions": "^5.1.0",
    "typescript": "^3.8.3"
  },
  "jest": {
    "preset": "react-native",
    "moduleFileExtensions": [
      "ts",
      "tsx",
      "js",
      "jsx",
      "json",
      "node"
    ]
  }
}

Issue Analytics

State:
Created 3 years ago
Comments:8 (2 by maintainers)

Top GitHub Comments

1reaction

jpdrivercommented, Oct 30, 2021

thanks all for sharing the updates here! 🙇🏻‍♂️

this is our current intended behaviour – this library will validate and ensure correct usage of a11y props when they are in use, but it doesn’t force you to implement the props every single time you use a <Touchable*/> or <Pressable /> component.

1reaction

majirosstefancommented, Aug 1, 2021

Just to save few minutes to somebody else, I have figured it out - you need to add accessibilityLabel manually, then linting works - it says you are missing some additional props. (My expectation was that it works on all TouchableOpacity / Pressable, TouchableHiglights, etc by default).

Top Results From Across the Web

Weather warnings on the go! - National Weather Service

WEA are very short messages designed to get your attention in an emergency situation. They may not give all the details you receive...

Emergency Alerts | Ready.gov

This page describes the different warning alerts you can get when emergencies strike and how to get them. Wireless Emergency Alerts ...

Manage warnings about unsafe sites - Google Chrome Help

You'll see a warning if the content you're trying to see is dangerous or deceptive. These sites are often called "phishing" or "malware"...

No Warning Labels on Products Can Lead to a Failure to ...

Sometimes it is because there is insufficient space on the product itself to fully warn. Other times, manufacturers may fear scaring off customers,...

Enable or disable security alerts on the Message Bar

Security Warning Message Bar for macros. Protected View from file validation failure. If you don't want security alerts, you can disable the Message...