pzyon / engraved Goto Github PK

• Marked text is currently not visible
• Shortcut to save (might not be necessary with autosave?)
• Autosave
• Falls asleep after a couple of minutes - WTF!?
• Border of markdown editor when active
• "Flackern" while typing (only in workplace?)
• "Root" bullets are not fully visible
• Consider introducing something like "sections" (with background)
• Consider introducing table of contents (ToC)
• Prevent users from navigating away when there are unsaved changes
• When creating a new note,
  • go directly to edit page
  • show "not saved" instead of nothing (in place of where "edited on" was last saved
• How to edit note title?

Affects

• UI
  • Give permissions
  • Manage permissions
  • Display in list and details
• API
  • Query metrics
  • Query measurements
  • Updates (when non owner)

Consider

• IHavePermissions interface
• PermissionKind (read, write)

• Dependabot
• Renovatebot

• Make overview items less crowded, e.g. move action icons to bottom

• Make group (i.e. day) collapsible and only show totals when collapsed

Similar to engraved.

• Link to github (commit hash?)
• Version number (api and app?)
• Release date

This is meant as an ongoing task for all things related to code quality.

• prettier
• ts/es lint
• new JSX transform

• Environment settings like URLs, etc.
• Pipeline: Prevent PR on error
• Pipeline: Make sure all triggers work correctly (push and pr, etc.)
• Pipeline: Make sure closing a PR successfully creates a release
• Pipeline (App.yml): Prevent success on lint/prettier error
• Skip not required builds: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks

Happens on mobile when switching from detail to overview to other detail. On second detail first detail is rendered quickly.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: packageRules[0]: Each packageRule must contain at least one match* or exclude* selector. Rule: {"automerge":true}

• Theming: https://mui.com/customization/theming/#theme-provider
• Error handling: https://mui.com/components/snackbars/
• Caching of data? E.g. when metric is already available from overview vs when navigating to the metric page directly via URL. In the second case, it needs to be fetched, in the first not.
• Lazy loading certain components (e.g. chartjs- and datagrid-stuff)

• E.g. columns in table:
• Information in overview
• Summary information

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update dependency @types/node to v20.14.5
• fix(deps): update dependency eslint to v9

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• chore(deps): update dependency ubuntu to v22

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

• Show first/last date (i.e. since when is this metric active?)
• Measurements count
• Stats (average and co.)

• Define two kinds of periods, e.g. "Year" could mean "current" or "rolling" (i.e. last 365 days)
• Filters on mobile are not really nice to use

• Show daily total (maybe make this generic [for all metrics] and toggable)
• Show current timer in
  • title?
  • measurements list
• Fix "edit measurment"-dialog
  • At the moment it shows button label (i.e. "Stop timer") depending on state of current timer (is running or not)
  • Add possibility to manually change time

Questions:

• Technical: Do we really still need a timer_start and timer_end endpoint? Couldn't all of this be handled by "upsert"?

• Choose visualization type
• Show metric info
• Summary-tab
• Think about "record metric" page/component

Possible use cases

• Weight loss, body temperature [value/gauge]
• Migraine days [counter]
• How long does my child take to go to sleep? [timed value]
• Endless games (e.g. "Pärli-Jassen")

Technical

Counter:

• Always increments by one
• Cannot be negative
• Might not have a concrete value

Gauge:

• A numerical value

Timer:

• A time duration
• Might need a start- and end-date, but maybe this can be implied based on metric-date

Further possible types

• Timestamp: E.g. when did my child go to sleep

Representation in UI:

• Show measurements table with appropriate fields
• Show relevant props in overview
  • Is running for timers
  • Number of measurements
  • Last measurement date
• Consider using icons to represent type (PlusOneSharp, BarChartSharp, TimerSharp)
  • On details page
  • In overview
  • Maybe even in add measurements? Or in Type picker?

And add an own implementation. Consider adding possibility to edit measurements or even add new ones.

Don't forget to remove dependency (package.json)

Similar as in many other apps, e.g. Todoist. Maybe for the beginning all we need is a text field (with basic markdown support?) that can be filled with whatever the user wants. In future we could consider adding multiple comments, that can be archived, etc.

Why do we need this?
So we can write some notes that are general related to that metric, e.g. à la "remember to add payments from XX" or "started medicine break on XX", etc.

E.g. https://react-query.tanstack.com/guides/queries

• Ordering of pills for consistency
• Gauge metric
  • Unit for Gauge metrics? E.g. currency.
  • Grouping?
• Labels for axes?
• Timer Meric:
  • Edit start and end date
  • Axis label (in hh:mm instead if absolute mins)
  • Duration field in measurements list must be hh:mm
• General
  • Why do axis labels have same values (e.g. see metrics/62bcbb28f975348cb5f8a2a0 on prod)?
  • Floatable "Plus" to easily add measurement
  • Make clicking a label (in donught and maybe stacked bar) toggle filter
  • Consider using loader buttons: https://mui.com/material-ui/react-button/#loading-button (attention: requires @mui/lab)

• Define threshold for a period, e.g. month, day, etc.

• Consider storing info regarding measurements on metric
  • e.g. last measurement, total measurements, etc.
  • or type specific stuff like "is running" for TimerMeasurements
  • This info could also be displayed in the overview
  • Possible server-side implementation: IDictionary<string, string> props? With setters and getters

actions/runner-images#5949

Required info (for display on client):

• Commit hash
• Version number
• Date

Notes

Set assembly version:
dotnet build --configuration Release -p:AssemblyVersion=123
dotnet build --configuration Release -p:AssemblyVersion=123 -p:SourceRevisionId=xxx+yyy -p:Version=333

Environment variables:
https://docs.github.com/en/actions/learn-github-actions/environment-variables
https://docs.github.com/en/actions/learn-github-actions/contexts#github-context

Example from Scott:
https://www.hanselman.com/blog/adding-a-git-commit-hash-and-azure-devops-build-number-and-build-id-to-an-aspnet-website