anki/rslib/src/search/mod.rs

// Copyright: Ankitects Pty Ltd and contributors
// License: GNU AGPL, version 3 or later; http://www.gnu.org/licenses/agpl.html

mod cards;
mod notes;
mod parser;
mod sqlwriter;
pub(crate) mod writer;

pub use cards::SortMode;
pub use parser::{
    parse as parse_search, Node, PropertyKind, RatingKind, SearchNode, StateKind, TemplateKind,
};
pub use writer::{concatenate_searches, replace_search_node, write_nodes, BoolSeparator};
NF: add AGPL licence missing in some file I noticed it when I looked at some files now used in AnkiDroid, wanting to be sure we clearly indicate that we have AGPLv3 code linked in the app 2021-01-31 21:50:21 +01:00			`// Copyright: Ankitects Pty Ltd and contributors`
			`// License: GNU AGPL, version 3 or later; http://www.gnu.org/licenses/agpl.html`

prototype of integration no ordering yet, and no tests 2020-03-19 23:20:47 +01:00			`mod cards;`
add note searching 2020-03-21 00:00:05 +01:00			`mod notes;`
basic search parsing 2020-03-15 10:11:45 +01:00			`mod parser;`
prototype of integration no ordering yet, and no tests 2020-03-19 23:20:47 +01:00			`mod sqlwriter;`
rework filtered deck screen & search errors - Filtered deck creation now happens as an atomic operation, and is undoable. - The logic for initial search text, normalizing searches and so on has been pushed into the backend. - Use protobuf to pass the filtered deck to the updated dialog, so we don't need to deal with untyped JSON. - Change the "revise your search?" prompt to be a simple info box - user has access to cancel and build buttons, and doesn't need a separate prompt. Tweak the wording so the 'show excluded' button should be more obvious. - Filtered decks have a time appended to them instead of a number, primarily because it's easier to implement. No objections going back to the old behaviour if someone wants to contribute a clean patch. The standard de-duplication will happen if two decks are created in the same minute with the same name. - Tweak the default sort order, and start with two searches. The UI will still hide the second search by default, but by starting with two, the frontend doesn't need logic for creating the starting text. - Search errors now have their own error type, instead of using InvalidInput, as that was intended mainly for bad API calls. The markdown conversion is done when the error is converted from the backend, allowing errors to printed as a string without any special handling by the calling code. TODO: when building a new filtered deck, update_active() is clobbering the undo log when the overview is refreshed 2021-03-24 12:52:48 +01:00			`pub(crate) mod writer;`
prototype of integration no ordering yet, and no tests 2020-03-19 23:20:47 +01:00
start work on field changes, and add search_cards to col 2020-04-14 08:47:26 +02:00			`pub use cards::SortMode;`
more search bikeshedding While implementing the overdue search, I realised it would be nice to be able to construct a search string with OR and NOT searches without having to construct each part individually with build_search_string(). Changes: - Extends SearchTerm to support a text search, which will be parsed by the backend. This allows us to do things like wrap text in a group or NOT node. - Because SearchTerm->Node conversion can now fail with a parsing error, it's switched over to TryFrom - Switch concatenate_searches and replace_search_term to use SearchTerms, so that they too don't require separate string building steps. - Remove the unused normalize_search() - Remove negate_search, as this is now an operation on a Node, and users can wrap their search in SearchTerm(negated=...) - Remove the match_any and negate args from build_search_string Having done all this work, I've just realised that perhaps the original JSON idea was more feasible than I first thought - if we wrote it out to a string and re-parsed it, we would be able to leverage the existing checks that occur at parsing stage. 2021-02-11 08:11:17 +01:00			`pub use parser::{`
			`parse as parse_search, Node, PropertyKind, RatingKind, SearchNode, StateKind, TemplateKind,`
Add native enum for concatenate_search's separator 2021-01-07 12:50:57 +01:00			`};`
tweak search wording and tidy up API - SearchTerm -> SearchNode - Operator -> Joiner; share between messages - build_search_string() supports specifying AND/OR as a convenience - group_searches() makes it easier to negate 2021-02-11 10:57:19 +01:00			`pub use writer::{concatenate_searches, replace_search_node, write_nodes, BoolSeparator};`