Files
KaTeX/.flowconfig
Kevin Barabash 151376e8aa Port katex-a11y.js to KaTeX (#2062)
* copy katex-a11y.js from webapp to contrib/to-a11y-string.js

* first pass of updating to-a11y-string to use flow

* Set up test harness and write some tests
- add flow types for jest
- create wallaby config file
- add prettier as a dep and set up .prettierrc so that we use .toMatchInlineSnapshot() and have jest insert the snapshot for us
- add lots of TODOs (I'll create tickets for these later)

* Add some  to get the tests passing for now

* remove commented out parts of wallaby.js config file

* remove some stale strings, fix flow issue, add more coverage

* add , add few more tests, handle middle

* fix minor nits in tests

* rename to-a11y-string to render-a11y-string, updatte webpack config to build extension

* add test for \boxed

* remove commented out code
2019-08-02 11:24:51 -04:00

31 lines
1.0 KiB
Plaintext

[version]
0.102.0
[ignore]
<PROJECT_ROOT>/dist
[include]
[libs]
[lints]
[options]
# $FlowFixMe
# This suppression hould be used to suppress an issue that requires additional
# effort to be resolved. That effort should be recorded in our issue tracking
# system for follow-up. Usually, this suppression is added by tooling during
# flow upgrades and should not be used directly by developers. If it is
# necessary, make sure to raise the corresponding issue and add the issue
# number to a TODO comment associated with the suppression.
suppress_comment=\\(.\\|\n\\)*\\$FlowFixMe
# $FlowIgnore
# Every now and then, flow cannot understand our code the way we can. We just
# know better and we have to tell flow to trust us. Since this isn't something
# we expect to "fix", we can annotate them to just have flow ignore them.
# Using this suppression makes it clear that we know there's an error but it's
# ok to ignore it. Make sure the suppression has associated commentary to state
# why it's okay to ignore the flow error.
suppress_comment=\\(.\\|\n\\)*\\$FlowIgnore