- Log in to post comments
Software developer with solid experience in the Intersystems IRIS platform and strong proficiency in ObjectScript, focused on code quality, software architecture, test automation, TDD, CI/CD, DevOps, and GitOps, all within agile methodologies. While holding the title of Mid-Level Developer, I consistently took on responsibilities beyond the role, including architectural decisions, technical mentoring, and process improvement. In parallel, I manage my own home server environment, gaining hands-on experience with open-source infrastructure tools such as Linux, Docker, Podman, Proxmox, Nextcloud, Prometheus, Grafana, Portainer, Nginx, and Cloudflare, deepening my understanding of networking, security, and service orchestration. I'm also an open-source enthusiast, developing full stack personal projects available on my GitHub. These include technologies such as React with TypeScript, Node.js with TypeScript, Python (Flask), .NET, Angular, Flutter, React Native, Bash scripting, and Docker. My goal is to learn, share, and build scalable, well-structured software.
Thank you for the feedback!
That is indeed an interesting feature, but like you said it could come with certain risks... However, as the implementation follows the single-responsability principle (each classmethod is responsible for getting a certain entity's data and nothing else), it wouldn't be difficult to add checkboxes on the extension's pop-up and query only chosen resources.
This wouldn't allow for custom entities per se, but it would allow for the addition of many other entities to the API without diminishing performance or cluttering the report for people who only care about a few of them. I'll definitively add this to my to-do!
And just a reminder, this project is 100% open source, so anyone is welcome to fork it and add custom resources to fit more specific needs like quering custom tables and such :)