feat: first commit

.dockerignore

@@ -0,0 +1,5 @@
+*
+!crates/
+!Cargo.toml
+!Cargo.lock
+.env

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,73 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting us via [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org

.github/CONTRIBUTING.md

@@ -0,0 +1,85 @@
+# Contributing to Yōzefu
+
+These guidelines apply to all projects living in the the `MAIF/yozefu` repository.
+
+These guidelines are meant to be a living document that should be changed and adapted as needed.
+We encourage changes that make it easier to achieve our goals in an efficient way.
+
+## Codebase
+
+* [lib](https://github.com/MAIF/yozefu/crates/lib): contains the core structures and the search module.
+* [app](https://github.com/MAIF/yozefu/crates/app): contains the kafka consumer with utility functions.
+* [tui](https://github.com/MAIF/yozefu/crates/tui): the glue code between `app` and Ratatui.
+* [wasm-types](https://github.com/MAIF/yozefu/crates/wasm-types): type definitions for defining WebAssembly modules.
+* [command](https://github.com/MAIF/yozefu/crates/command): commands for the CLI.
+* [bin](https://github.com/MAIF/yozefu/crates/bin): the binary.
+
+## Workflow
+
+The steps below describe how to get a patch into a main development branch (e.g. `main`). 
+The steps are exactly the same for everyone involved in the project (be it core team, or first time contributor).
+We follow the standard GitHub [fork & pull](https://help.github.com/articles/using-pull-requests/#fork--pull) approach to pull requests. Just fork the official repo, develop in a branch, and submit a PR!
+
+1. To avoid duplicated effort, it might be good to check the [issue tracker](https://github.com/MAIF/yozefu/issues) and [existing pull requests](https://github.com/MAIF/yozefu/pulls) for existing work.
+   - If there is no ticket yet, feel free to [create one](https://github.com/MAIF/yozefu/issues/new) to discuss the problem and the approach you want to take to solve it.
+2. [Fork the project](https://github.com/MAIF/yozefu#fork-destination-box) on GitHub. You'll need to create a feature-branch for your work on your fork, as this way you'll be able to submit a pull request against the mainline branch.
+3. Create a branch on your fork and work on the feature. For example: `git checkout -b wip-awesome-new-feature`
+   - Please make sure to follow the general quality guidelines (specified below) when developing your patch.
+   - Please write additional tests covering your feature and adjust existing ones if needed before submitting your pull request. 
+4. Once your feature is complete, prepare the commit with a good commit message, for example: `Adding nice feature #42` (note the reference to the ticket it aimed to resolve).
+5. Now it's finally time to [submit the pull request](https://help.github.com/articles/using-pull-requests)!
+    - Please make sure to include a reference to the issue you're solving *in the comment* for the Pull Request, this will cause the PR to be linked properly with the Issue. Examples of good phrases for this are: "Resolves #1234" or "Refs #1234".
+6. Now both committers and interested people will review your code. This process is to ensure the code we merge is of the best possible quality, and that no silly mistakes slip through. You're expected to follow-up these comments by adding new commits to the same branch. The commit messages of those commits can be more loose, for example: `Removed debugging using printline`, as they all will be squashed into one commit before merging into the main branch.
+    - The community and team are really nice people, so don't be afraid to ask follow up questions if you didn't understand some comment, or would like clarification on how to continue with a given feature. We're here to help, so feel free to ask and discuss any kind of questions you might have during review!
+7. After the review you should fix the issues as needed (pushing a new commit for new review etc.), iterating until the reviewers give their thumbs up-which is signalled usually by a comment saying `LGTM`, which means "Looks Good To Me". 
+8. If the code change needs to be applied to other branches as well (for example a bugfix needing to be backported to a previous version), one of the team will either ask you to submit a PR with the same commit to the old branch, or do this for you.
+9. Once everything is said and done, your pull request gets merged. You've made it!
+
+The TL;DR; of the above very precise workflow version is:
+
+1. Fork yozefu
+2. Hack and test on your feature (on a branch)
+3. Document it
+4. Submit a PR
+6. Keep polishing it until received thumbs up from the core team
+7. Profit!
+
+## External dependencies
+
+All the external runtime dependencies for the project, including transitive dependencies, must have an open source license that is equal to, or compatible with, [Apache 2](http://www.apache.org/licenses/LICENSE-2.0).
+
+This must be ensured by manually verifying the license for all the dependencies for the project:
+
+1. Whenever a committer to the project changes a version of a dependency (including Scala) in the build file.
+2. Whenever a committer to the project adds a new dependency.
+3. Whenever a new release is cut (public or private for a customer).
+
+Which licenses are compatible with Apache 2 are defined in [this doc](http://www.apache.org/legal/3party.html#category-a), where you can see that the licenses that are listed under `Category A` are automatically compatible with Apache 2, while the ones listed under `Category B` need additional action:
+
+> Each license in this category requires some degree of [reciprocity](http://www.apache.org/legal/3party.html#define-reciprocal); therefore, additional action must be taken in order to minimize the chance that a user of an Apache product will create a derivative work of a reciprocally-licensed portion of an Apache product without being aware of the applicable requirements.
+
+Each project must also create and maintain a list of all dependencies and their licenses, including all their transitive dependencies. This can be done either in the documentation or in the build file next to each dependency.
+
+
+## Getting started
+
+The easiest way to create a dev workspace is to run the following commands:
+
+```bash
+bash docs/try-it.sh "Nantes" "json" "public-french-addresses-json"
+bash docs/try-it.sh "Narbonne" "jsonSchema" "public-french-addresses-json-schema"
+bash docs/try-it.sh "Niort" "avro" "public-french-addresses-avro"
+bash docs/try-it.sh "Nancy" "text" "public-french-addresses-text"
+bash docs/try-it.sh "Nimes" "malformed" "public-french-addresses-malformed"
+cargo run -- -c localhost
+```
+
+`try-it.sh` is a script booting a kafka instance and a schema registry with docker. Plus, it publishes json data to a default topic.
+
+## Tests
+
+Every new feature should provide corresponding tests to ensure everything is working and will still working in future releases. To run the tests, just run
+
+```sh
+cargo test --all-features
+```

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,29 @@
+---
+name: Bug report
+about: Create a bug report
+title: ''
+labels: ''
+assignees: ''
+
+---
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Run `--topics my-topics 'from begin'`
+2. Select the kafka record X...
+3. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**version:**
+[e.g. v0.1.0]
+
+**Additional context**
+Additional information that may be relevant to the issue.
+[e.g. architecture, OS]

.github/dependabot.yml

@@ -0,0 +1,11 @@
+version: 2
+updates:
+  - package-ecosystem: "cargo"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "monthly"

.github/workflows/actionlint.yml

@@ -0,0 +1,20 @@
+name: Actionlint
+
+on:
+  workflow_dispatch:
+  push:
+    paths:
+      - .github/workflows/**
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:  
+  actionlint:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+      - name: actionlint
+        uses: raven-actions/[email protected]