opengovsg / ctrl-shift Goto Github PK

Using an in-memory H2 database causes customer demos to be wiped after every deploy. Ideally, they would still be available for potential customers to play around with after the meeting.

Hello,

I just added "weekOfDay" of a person to Employee entity, and trying to make the Employee UNAVAILABLE on the thay specified with entity.

One way is to write a rule, other is to set unavailability with each rotation (from the beggining).

I'm confused here, because already a rule exist to check of unavailability of a employee, I don't want to write same rule and jsut make it to check whether the day is the "weekOfDay" or not. But, I couldn't achieve to make second option?

Any help on that?

Thanks in advance.

Implement a night mode toggle for easier reading during night shift operations

Our repo already has SonarCloud integration. By subscribing to it, we can continue to scan our code for vulnerabilities for $10/mth - it's even free if we open source.

We can also display our own badges in the readme, currently they're pointing to upstream:

Users may have different time horizons when looking at a shift, so allow them to adjust the time interval to view, through the date interval picker, which has to be fixed

App should not be publicly accessible without password
No need for tenant segregation (multiple accounts) yet

US2: User can upload employees and skills in .csv

@LoneRifle need to think about the user flow, because replacing employees will disrupt existing rosters (incl. those that have been published) due to cascading deletes in the database. Maybe only allow this at the point of roster creation?

@LoneRifle Understand data model

We need a project email or mailing list e.g. [email protected] to sign up for various services instead of using our own email accounts. Can look for pallani or liwei to set up.

Currently the Hibernate ORM will automatically update the database schema on connection to DB due to spring.jpa.hibernate.ddl-auto=update being set in application.properties. This is dangerous and should be disabled before launching as a production application.

Today we don't have an online demo app, it has to be run on localhost. We need to procure a cloud account and set up a CD pipeline.

How do we slot an employee in at the last minute while minimizing the number of changes to take place in rescheduling?

• Create unrostered shift from date:time to date:time (could span more than 1 calendar date or 24h)
• Set repetition every n days
• Set end-date

Like #42 but for availabilities

• Create availability (unavailable/desired/undesired) from date:time to date:time
• Set to repeat every n days
• Set end-date

We're not deploying to RedHat clusters.