Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All operations around PlanoConta are implemented (full CRUD) #14

Merged
merged 12 commits into from
Dec 20, 2024

Conversation

disouzam
Copy link
Member

  1. 759ecf0 Simple Javascript functions to simulate actions in Editar and Excluir buttons

  2. 48096e7 Fixed Voltar function to account for two routes using the same UI - insert new PlanoConta and editing existing one

  3. 4b4c542 Implemented function under button Editar to go to Cadastro page with an existing PlanoConta

  4. 8ca2658 Mocked endpoint that returns one PlanoConta item for edition

  5. 3566cb7 Started implementation of editing functionality - Retrieval of existing PlanoContaModel is completed

  6. a0596c6 Modified PlanoContaService to get id of newly saved PlanoConta and retrieve it after saving in database

  7. 5bf9dcd Implemented actions for updating a PlanoConta item

  8. bad9e62 Retrieved the request item id and saved to item to be returned by the extension method ConvertToPlanoConta

  9. bd41167 Added a discard operator in the action that saves a new item and returned a RedirectToAction to go back to the list with all PlanoConta items

  10. a061963 Implemented exclusion of PlanoConta with consideration for some forbidden exclusions

    • Forbidden exclusions are those of PlanoConta items that serve as a foreign key for transactions.
    • In current implementation there is no error message for the user when exclusion is not possible nor success message when exclusion is performed
  11. bb2a0f0 Routes in PlanoContaController for full functions to work fine

… insert new PlanoConta and editing existing one
…rned a RedirectToAction to go back to the list with all `PlanoConta` items
…dden exclusions

- Forbidden exclusions are those of PlanoConta items that serve as a foreign key for transactions.
- In current implementation there is no error message for the user when exclusion is not possible nor success message when exclusion is performed
    -   In the context of ASP.NET Core MVC web applications, both model binding and model validation are processes that take place prior to the execution of a controller action. It is imperative for the application to examine the ModelState.IsValid and respond accordingly.
        This rule enforces the developer to validate the model within a controller action, ensuring the application’s robustness and reliability.
    - https://rules.sonarsource.com/csharp/tag/asp.net/RSPEC-6967/
@disouzam disouzam merged commit 9e81dbb into main Dec 20, 2024
5 checks passed
@disouzam disouzam deleted the Aula6-FinalImplementations branch December 20, 2024 15:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant