Skip to content

Commit

Permalink
fix dict?
Browse files Browse the repository at this point in the history
  • Loading branch information
owestphal committed Jul 31, 2023
1 parent dd4eebd commit 13a99e7
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions .github/workflows/spelling.yml
Original file line number Diff line number Diff line change
Expand Up @@ -61,8 +61,8 @@ jobs:
cspell:filetypes/filetypes.txt
cspell:software-terms/src/software-terms.txt
cspell:companies/src/companies.txt
cspell:haskell/haskell.txt
cspell:html/html.txt
cspell:haskell/dict/haskell.txt
cspell:html/dict/html.txt
cspell:de_DE/de_DE.trie

comment:
Expand Down

1 comment on commit 13a99e7

@github-actions
Copy link

@github-actions github-actions bot commented on 13a99e7 Jul 31, 2023

Choose a reason for hiding this comment

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

@check-spelling-bot Report

🔴 Please review

See the 📜action log for details.

Unrecognized words (76)
Anzahl
atempt
AVars
bdy
beendet
beiden
Bifunctor
cmp
concat
ctx
CVars
drei
durch
ein
eine
Eingaben
evl
exs
eys
fmap
foldr
fprop
fst
geben
GHC
hhh
HRefl
hspec
implicits
ints
IOrep
len
letzten
linebreak
mconcat
mempty
mergesort
MTT
Mul
Naechste
nats
noch
nop
NOut
NProg
NTerminate
NTrace
nums
Occured
oneof
overfl
Perfprop
positiven
Programm
propertiy
SATs
snd
standalone
Subterms
Summe
teilbaren
thd
TQueue
TVar
uncurry
unfoldings
unlines
unrwarp
Unsat
unwords
vals
varname
vcat
xit
xprop
xss
To accept ✔️ these unrecognized words as correct, run the following commands

... in a clone of the [email protected]:fmidue/IOTasks.git repository
on the fix-spell-checking branch (ℹ️ how do I use this?):

update_files() {
perl -e '
my $new_expect_file=".github/actions/spelling/expect.txt";
use File::Path qw(make_path);
use File::Basename qw(dirname);
make_path (dirname($new_expect_file));
open FILE, q{<}, $new_expect_file; chomp(my @words = <FILE>); close FILE;
my @add=qw('"$patch_add"');
my %items; @items{@words} = @words x (1); @items{@add} = @add x (1);
@words = sort {lc($a)."-".$a cmp lc($b)."-".$b} keys %items;
open FILE, q{>}, $new_expect_file; for my $word (@words) { print FILE "$word\n" if $word =~ /\w/; };
close FILE;
system("git", "add", $new_expect_file);
'
}

comment_json=$(mktemp)
curl -L -s -S \
-H "Content-Type: application/json" \
"https://api.github.com/repos/fmidue/IOTasks/comments/123192079" > "$comment_json"
comment_body=$(mktemp)
jq -r ".body // empty" "$comment_json" | tr -d "\\r" > $comment_body
rm $comment_json

patch_add=$(perl -e '$/=undef; $_=<>; if (m{Unrecognized words[^<]*</summary>\n*```\n*([^<]*)```\n*</details>$}m) { print "$1" } elsif (m{Unrecognized words[^<]*\n\n((?:\w.*\n)+)\n}m) { print "$1" };' < "$comment_body")

update_files
rm $comment_body
git add -u
Errors (1)

See the 📜action log for details.

❌ Errors Count
❌ candidate-pattern 4

See ❌ Event descriptions for more information.

If the flagged items are 🤯 false positives

If items relate to a ...

  • binary file (or some other file you wouldn't want to check at all).

    Please add a file path to the excludes.txt file matching the containing file.

    File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.

    ^ refers to the file's path from the root of the repository, so ^README\.md$ would exclude README.md (on whichever branch you're using).

  • well-formed pattern.

    If you can write a pattern that would match it,
    try adding it to the patterns.txt file.

    Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.

    Note that patterns can't match multiline strings.

Please sign in to comment.