tomassasovsky / weappe.ar Goto Github PK

View Code? Open in Web Editor NEW

5.0 2.0 0.0 3.73 MB

Open-Source time logger backend made in Dart

License: MIT License

Shell 0.82% Dockerfile 0.80% Dart 97.96% Batchfile 0.41%

dart timelogging

weappe.ar's Introduction

weappe.ar's People

Contributors

Stargazers

Watchers

weappe.ar's Issues

feat: add privacy settings to organizations to selectively show logs publicly

feat: validator helper class for middlewares

the class should have helpers to grab specified variables sent (from the HttpRequest) and cast them as a specific variable type. should also have the capability of being optional/required

Return a list of Clock in/out's from user id and from organization id

This is to easily get all the clock in/out's an user created for an organization.

feat: invites

An organization should be able to invite a person to join not only the organization itself but also the platform. it should contain:

email
type of user (employee, employer)
inviteRef (part of the URL that will be used to refer to that specific invite)
a time limit - hardcoded 7 days for MVP

feat: validate users emails

Right now if a user want to use another's person email it can because we're not validating it. So if a user is not validated, it shouldn't be able to login.

feat: implement 2FA to improve security

Security it's one of the most important thing for us, so having 2FA will give our users the security they need.

performance test and comparison with nodejs (expressjs)

hotfix: career condition on new inserts for users in organizations, and possible duplicates on every collection

This should be fixed by implementing schema validation for the collections and creating a unique index where fitting.

see mongo-dart/mongo_dart#282 and mongo-dart/mongo_dart#283 for some guidance.

feat: Clock-In/Out

Users (whether they be employees or employers), should be able to clock in and clock out with a simple click.

Additional information on what tasks they've been working on is optionally required by the organization (or their settings, if they aren't in an organization).

feat: Categories/Subcategories/Tasks for clock in/out

Categories, subcategories, and specific tasks can be assigned by the organization to the user. After that, the user can select which category/subcategory/task they were working on at a specific time. Templates for this will also have to be made and provided to the organizations by us, the developers, to ease the process of creating one a tad.

Would look like this:

abstract class RouteHandler<T extends RouteHandler<T>> {
  FutureOr<dynamic> defineVars(HttpRequest req, HttpResponse res) async {}

  // this is the method that is called when the route is called
  FutureOr<dynamic> call(HttpRequest req, HttpResponse res) async {
    final instance = newInstance;
    // this handles the request
    await instance.defineVars(req, res);
    req.validate();
    await instance.run(req, res);
  }

  FutureOr<dynamic> run(HttpRequest req, HttpResponse res);

  // to create a new instance internally
  T get newInstance;
}

and an implementation of this:

class SomeMiddleware extends Middleware<SomeMiddleware> {
  @override
  FutureOr run(HttpRequest req, HttpResponse res) {}

  @override
  SomeMiddleware get newInstance => SomeMiddleware();
}

tomassasovsky / weappe.ar Goto Github PK

weappe.ar's Introduction

WeAppe.ar

About The Project

Built With

Getting Started

Prerequisites

Setting up the project

Deploying

Endpoints and Usage

Roadmap

Testing

Features

Contributing

License

Contact

weappe.ar's People

Contributors

Stargazers

Watchers

weappe.ar's Issues

Recommend Projects

Recommend Topics

Recommend Org