This was done because setting up a test even as an example was hard with
the dependencies and other things. It may be doable, but the time
required was not worth it.
The SQL was not properly searching the tales. It had been searching and
finding all the tags that matched the search criteria, but it was
dropping all the other tag information. Now it properly keeps all the
tag information. This fixed an issue where the tags of a post were
disapearing and reapearing as the TagSelector was toggled.
When using dioxus it would be greate to use the types from this library
on the backend and the front end. To do this we need to be able to cut
out the sqlx package because it uses mio which doesn't compile to WASM.
To do this we put the database code behind a database feature flag.
The Publisher feature will also trigger the database flag.
**tavern** - The blogging system library.
**loremaster** - Creates the database from a blogging repository.
**bard** - Dioxus components to display the blog.
It was determined that Async database access would be prefereable incase
we decide to use a network database instead of sqlite.
Tests and examples need to be checked, but they were made to build.
Posts and Authors can now be inserted and retrieved from the database
created. It was decided to use a SQLite database for it high read spead
and ease of use/maintenance.
A build feature was created to seperate how the library is being used.
If you are making the database and storing posts, then use the publisher
flag. If you are just reading from a database then do not use the
publisher flag. This was also set to change the tale contents from a
PathBuf to the String of HTML blog data without having to create a whole
new data object.
An example and a test were made. Test coverage needs to be increased
however.
