-
Anton Shestakov <av6@dwimlabs.net>, Mon, 20 Jun 2016 00:11:57 +0800
incoming: use a list of regular expressions to extract linter output type
-
Anton Shestakov <av6@dwimlabs.net>, Sun, 19 Jun 2016 23:51:50 +0800
incoming: move linter output matching to a function, test it
-
Anton Shestakov <av6@dwimlabs.net>, Sun, 19 Jun 2016 23:44:42 +0800
tests: pass extra arguments given to run-tests.py into pytest.main()
-
Anton Shestakov <av6@dwimlabs.net>, Sun, 19 Jun 2016 22:04:57 +0800
incoming: save filename and line number for linter output in Check.lines
-
Anton Shestakov <av6@dwimlabs.net>, Sun, 19 Jun 2016 22:03:36 +0800
incoming: use dicts instead of tuples for Check.lines
-
Anton Shestakov <av6@dwimlabs.net>, Sun, 19 Jun 2016 16:22:28 +0800
models: add Project.get_title() method, use it, test it
-
Anton Shestakov <av6@dwimlabs.net>, Sun, 19 Jun 2016 15:52:04 +0800
incoming: parse_project_url() function to extract domain, user and name, tests
-
Anton Shestakov <av6@dwimlabs.net>, Sun, 19 Jun 2016 14:41:11 +0800
viewer: use a lineno class to put styles on the line number links
-
Anton Shestakov <av6@dwimlabs.net>, Sun, 19 Jun 2016 14:16:56 +0800
incoming: only try to match linter output if it's not a meta line
-
Anton Shestakov <av6@dwimlabs.net>, Sun, 19 Jun 2016 14:07:11 +0800
incoming: skip checking the whole line when it's linter output
When a line starts with a certain pattern, it's recognized as linter output,
but determining if it's an error or a warning was done looking at the whole
string again multiple times. Let's save on regexes and look only on the
important part.