.NET Blazor Web Application Extension
Budget: $30 – $250 USD
Seeking a skilled developer to fork and extend a .NET 8 Blazor web application based on an existing open source repository. The ideal candidate will have experience with Blazor and .NET development, and be able to implement new features and enhancements efficiently. You will be responsible for understanding the current codebase, extending it to cater for a custom use-case and ensuring the application is robust and user-friendly. Strong communication skills and the ability to work independently are essential.
You will extend the current code base to enable the creation of a new type, dynamically, which can be configured in the same way as the existing resource types. It will persist as a new JSON collection and support the existing import/export mechanism. The new type/s will appear in the existing search and configured in the same way.
Extend the RESTful API for any new endpoint added + provide 2 examples of new types, each with their own RegEx pattern / configuration, persisted, exported and proven they work when imported from scratch.
It important that we can easily, dynamically, create a new set of rules, i.e via the RegEx and then pick a set of options, when applying, like dropdowns for env: i.e dev etc to build a unique set, just as the existing functionality is offered.
The new types will collaborate in the history, including detecting duplicates, just as the current solution operates.
https://github.com/mspnp/AzureNamingTool
You will extend the current code base to enable the creation of a new type, dynamically, which can be configured in the same way as the existing resource types. It will persist as a new JSON collection and support the existing import/export mechanism. The new type/s will appear in the existing search and configured in the same way.
Extend the RESTful API for any new endpoint added + provide 2 examples of new types, each with their own RegEx pattern / configuration, persisted, exported and proven they work when imported from scratch.
It important that we can easily, dynamically, create a new set of rules, i.e via the RegEx and then pick a set of options, when applying, like dropdowns for env: i.e dev etc to build a unique set, just as the existing functionality is offered.
The new types will collaborate in the history, including detecting duplicates, just as the current solution operates.
https://github.com/mspnp/AzureNamingTool