square/sqlbrite

Lint checks for runtime assertions and common errors.

Open

#58 opened on Sep 9, 2015

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Java (4,578 stars) (431 forks)batch import
help wantedicebox

Description

  • Creating a query inside of a transaction
  • Question marks in a query don't match number of arguments (#220)
  • Missing mark success in try/finally or try-with-resources
  • Multiple insert/update/delete statements not in a transaction in a single method
  • Ensure first argument looks like a table / list of tables
  • Second argument looks like SQL and contains all tables from the first argument

Contributor guide

Tech stack
javasql
Domain
toolingdeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaSQLiteAndroid lint framework
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
To add a lint check, you need to create a custom lint rule in Java using the Android lint API. Start by examining the existing checks in the repository or similar projects. The issue lists several concrete checks, such as 'Creating a query inside of a transaction' and 'Question marks in a query not matching arguments'. Each check can be implemented as a separate Detector class. Refer to the Android lint documentation for creating custom lint rules.