Sousmarin is not building on Travis because of the old version of Dart we are stuck to. We need to use the newest version of the language.

Design a nice screen showing all available details about a player

Now one has to type the exact family name of the player in order to find something. The idea is to offer a list of possible players while typing in the search field and to allow the user to select from there. Like in the web site www.aftnet.be

"Delattre Jean - Michel" wil lbe parsed as
first name: Michel
last name: Delattre Jean -

And that's not correct. Maybe removing the spaces around the dash?

Create a list view components usable for al objects in the application - players, clubs, matches etc.

Full info about the player's matches on his details page. Possibility to switch to other players (opponents)

Maybe it's enough to setState only of the playerItemWidget

Actually only search by name is possible. Would be good to have also search by id

Provide a beautiful design of the player's widget in the list view

Like:

• simple/double matches won/lost

Now we have PlayersHome, and PlayersList. PlayersList contains the definition the of Player's tile. Not the optimal and most intuitive organization. Maybe keeping only PlayersHome for the list definition and renaming PlayersList to PlayerListWidget or something will help.

Also, what if I put all Player related UI in a separate folder?

Add a mechanism to switch between screens and to go back with the button

An exception is thrown if one tries to tap in the heart icon in the players list

Currently only players from Brabant Wallon are shown

It's crucial for Belgium to have a reliable real time weather info

The following error can occur in the player_details screen:

[ERROR:topaz/lib/tonic/logging/dart_error.cc(16)] Unhandled exception:
E/flutter ( 5367): setState() called after dispose(): _PlayerDetailsState#36821(lifecycle state: defunct, not mounted)
E/flutter ( 5367): This error happens if you call setState() on a State object for a widget that no longer appears in the widget tree (e.g., whose parent widget no longer includes the widget in its build). This error can occur when code calls setState() from a timer or an animation callback. The preferred solution is to cancel the timer or stop listening to the animation in the dispose() callback. Another solution is to check the "mounted" property of this object before calling setState() to ensure the object is still in the tree.
E/flutter ( 5367): This error might indicate a memory leak if setState() is being called because another object is retaining a reference to this State object after it has been removed from the tree. To avoid memory leaks, consider breaking the reference to this object during dispose().