-
Przemyslaw Kaminski authored
For ngrams table, we set ngramsValidPatch = mempty because the table is refreshed and we have issue #594 However, we need to keep that field, it turns out, because we have #598 Recently applied patches are needed for the document ngrams highlighting. This all would be unnecessary (or at least moved to the backend) if we had #553
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| Components | ||
| Config | ||
| Context | ||
| Core/NgramsTable | ||
| Data | ||
| Hooks | ||
| Sessions | ||
| Text | ||
| Utils | ||
| AsyncTasks.purs | ||
| Classes.purs | ||
| Config.purs | ||
| Ends.purs | ||
| Hooks.purs | ||
| Prelude.purs | ||
| Router.purs | ||
| Routes.purs | ||
| Sessions.purs | ||
| Types.purs | ||
| Utils.purs |