thdk / team-timesheets Goto Github PK

When deploying firestore it shows the following warning:

firestore: your indexes indexes are specified in the v1beta1 API format. Please upgrade to the new index API format by running firebase firestore:indexes again and saving the result.

Current implementation is a bit messy and not future proof.

Click a registration to edit

Make the description field empty.

Click the delete icon in the top app bar.

Result: Show the overview page with the registration with an empty description field.
Expected result: The registration should have been deleted

Currently google authenticaton providers is hardcoded as the only allowed login provider.

It's should be configurable.

When copy pasting description from mantis, we often get whitespace before the actual text.

Users should only be allowed to read there own user document from the user collection.

Force a new "fingerprint" whenever the content of an output file has changed.

Ensures new changes are always visible when deploying new version.

Currently the default task is hard coded to "Programming"

User should be able to select his/her default task in the preferences tab of settings page.

The calendar control in the drawer menu should have an indication of the current selected day

ex. go to: https://timesheets-ffc4b.firebaseapp.com/timesheets/2018/12/25

The calendar control should indicate:

• the the selected date is 25th december (using a background color)
• the date of today should get another font color

(Note: bold dates mean there are registrations available for that date)

Currently config.ts file contains the firebase project settings and we need to change these settings every time we want to switch deploy to dev or production.

Manifest files allows user to add the web page to their homescreen.

When they launch from the homescreen, the web page will not have an address bar etc...
=> Looks like a native app

See screenshot:

Using the multi selection functionality added in #21 user should be able to copy/cut selected registrations.

The user should be able to paste those registrations in any day. All data should be taken from the source registrations, except for the date. The date should be taken from the current view (which can be the same as the date of the source when pasting copy pasting within the same day)

Currently the user store still fetches all users and then picks the data for the current logged in user.
Obviously this shouldn't be needed and shouldn't be allowed for security reasons anyway.

When user use ctrl + click (or double click to be mobile friendly?) on a registration entry, an indicator should display the number of selected registrations in the top app bar.

A button in the top app bar should allow to clear selection.

See contextual top app bar by material design:

Registration should only be displayed if it's saved

When updating fields of the user document of the logged in user, the changes are not reflected immediately but require a refresh.

=> user updates (such as defaultClient, defaultTask, recentProjects) should be immediately visible without needing a refresh

firebase setup:web

prints config for the current active firebase project in the console:

firebase.initializeApp({
  "apiKey": "xxxxxxxxxxxxxx",
  "databaseURL": "xxxxxxxxxxxx",
  "storageBucket": "xxxxxxxxxxxxxx",
  "authDomain": "xxxxxxxxxxxxxx",
  "messagingSenderId": "xxxxxxxxxxxxxx",
  "projectId": "xxxxxxxxxxxxxx"
});

It's much easier to use this than to go to the firebase console and copy paste the settings from there.
No need to leave VS Code.

User can limit the number of tasks to be displayed when he/she creates/edits a registrations.

When the user has not made any choices (yet) in the user preferences, he/she should see all the asks listen when creating/updating a registration.

Another option is to disable the settings page completely for unauthorized users

Will be used as favicon, launch icon, home screen icon, ...

When scrolling through the month overview with registrations, a usecase is that we often want to add/change something for a specific day. To do this, we need to click that day in the month overview and do the desired changes. From the day view, the link to go back to the month overview should include data to ensure we'll see the month overview with the last selected day in view.

when deploy hosting for productions the build script should be run with --env=production as a predeploy script so we don't accidentally deploy development environment variables in production.

https://firebase.google.com/docs/firestore/query-data/indexing

Idea is to add another button closer to the title of the current screen (day/month view)

But is it a good idea to have multiple buttons for the same purpose?