devonfw-forge / devon4flutter-non-bloc-arch Goto Github PK

Description
We would like to add some dummy data to the server in order to be able to test the application with

Acceptance Criteria

Description
Track the progress of the backend and write the updates continuously into this ticket in order to have everyone onboard with the updates.

Acceptance Criteria

As a user I would like ... in order to ...

Description
As a user I would like to be able to choose between a list view and a grid view.

Acceptance Criteria

1. In the list view the full name and email address should be displayed on the text fields

2. In the grid layout I want to have more information on the displayed cards than in the list view. The cards displayed on the grid layout should contain the following information:

• Put first and last name in bold at the top
• Add more information below in thin font (e.g. email address, profession etc.)

Description
As a user I would like my app to load the data from the server/mock in order to be able to have no static data in the app.

Acceptance Criteria

• The data that is in the BLOC Repository is loaded from the configured API/Mock on startup

As a user I would like ... in order to ...

Description
As a user I would like to customize the yaml file of the app.

Acceptance Criteria

• The yaml file should contain all variables of the app

Developer Hints

• https://www.w3schools.io/file/yaml-introduction/
• https://www.javatpoint.com/yaml
• https://www.educative.io/blog/yaml-tutorial

When you switch to dark mode, the cards and the text remain white.

Description
As a user I would like to have a dialog where I can add a new entry in order to later be able to send new entries to the server.

Acceptance Criteria

• The call to the server should be done in a later task
• OK button should be present but without function
• For each property in the model there should be an input field in the dialog

Description
As a user, I would like to have a sturdy routing in my application so that I could navigate from one page to the other easily and have the pages stack replaced when needed.

Acceptance Criteria

• The user shall be able to route from the main application page (Get Employees button) to the list of employees and then to a specific employee dialog if needed
• The user shall be able route back as well which means the pages stack shall remain the same along the user flow

Description
Create a splash screen for the app.

Acceptance Criteria

• Short timer duration
• Example logo
• Visually matching the app

Description
As a user I would like to have a dialog where I can change entities in order to change incorrect data.

Acceptance Criteria

• Add heading to the current page
• In the 'view entity' dialog there should be an edit button in the appbar that opens an edit dialog
• For each property in the model there should be an input field with the current value of the model
• When the user presses OK then the data is sent to the server
• In case of an error the user stays at the update dialog
• In case of success the user is taken to the show entity dialog

This is not an issue.But a suggestion that

This awesome guides could be turned to pdf,
Thanks.

Hey, first of all, great work! Good slab of text that details the development process quite accurately.
However, there is one nitpick I cannot ignore, and it is the difference between the BLoC pattern and the bloc library.

The library, fundamentally, is actually something many would describe as "Redux, but with smaller stores.".

1. It maps almost 1:1 in the items you interact with

• Events : Actions
• "bloc" : Store
• mapEventToState : Reducer

2. Uses a single stream output, exactly like Redux (Would this mean that Redux.dart is BLoC?)
3. One could argue that wrapping the input in an Action violates the 'Components should send inputs "as-is"'

There is even a proper description and example of a bloc as a source!

This line is, as far as I can tell, not accurate. The library is similar, but the pattern itself is not. Redux stands for a single source of truth modified by clearly defined, "static" actions that predictably change said single source of truth. BLoC stands for the power of streams, both in and out, in some cases even inside.

I'm not saying that the library is bad, it's widely used and proves to be reliable, however, it is a car pretending to be a bike.

As a user I would like to crate templates flawlessly. This would definitely be achieved by having templates tested for generated applications.

Description
As a user I would like to have a delete functionality in the app in order to remove unwanted entities.

Acceptance Criteria

• The list of entities should have the possibility to delete a single entity

Description
As a user I would like ... in order to ...

Acceptance Criteria

Description
As a user I would like ... in order to ...

Acceptance Criteria

As a user I would like ... in order to ...

Create an empty "Hello world" project. Commit it into the repository that's everyone from the team can start