Reto Nervo #4 Rust

[Vi-dot1]

Solución al reto #4 (file watcher) en Rust

✅ Checklist

• [ X ] Mi código está dentro de la carpeta correcta del reto
• [ X ] Agregué un README corto explicando cómo correr mi solución
• [ X ] Probé que mi código funciona antes de subirlo
• Es mi primera vez contribuyendo a un proyecto open source (opcional, ¡para celebrarlo!)
• Creo que esta solución está lo suficientemente pulida como para considerarse para "graduarse" a zenith-nerve-tools (opcional, no pasa nada si no marcas esto)

Capturas o gif (opcional pero recomendado)

💬 Notas para quien revise

Mi solución crea un nodo "FileWatcher" el cual enviá los cambios que ocurran a un archivo o carpeta usando notify, se asume que existe un nodo con nombre "Monitor" al cual notifica.

Los test son mayormente para mostrar como funciona, si se corren individualmente se puede ver impreso los eventos al cambiar el archivo.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​tokio@​1.53.1
	cargo/​alenia-nerve@​1.5.1
	cargo/​serde@​1.0.229
	cargo/​serde_json@​1.0.151
	cargo/​notify@​8.2.0

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: cargo tokio is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: retos/nerve/04-vigilante-de-carpetas/soluciones/Vidot1-Rust/Cargo.lock → cargo/tokio@1.53.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/tokio@1.53.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report