Introduce a TextField component under crates/web/lib/components directory.

Currently links can only have a random hash.
It would be great to have links with custom hashes.

Expected Input/Output:

mutation {
  linkCreate(input: {
    url: "https://www.google.com"
    customHash: "mi_link"
  }) {
    link {
      id
      hash
      originalUrl
      expiresAt
    }
  }
}

{
  "data": {
    "linkCreate": {
      "link": {
        "id": 2,
        "hash": "mi_link",
        "originalUrl": "https://www.google.com",
        "expiresAt": "1970-01-01T00:00:00+00:00"
      }
    }
  }
}

Source Code: https://github.com/whizzes/linx/blob/main/src/server/src/graphql/link/mutation/link_create.rs#L29

when posting to the /new route, the server should check if the body being passed to it is a url

Provide a Follow button for the User Profile UI at /[username].

I think that if the same url already exists on the server, it should deliver the hash created previously.

Provide more E2E tests on the user module.
Check on src/test crate for examples.

Provide better logging and responses for login on failures

Whenever a link is redirected we must store useful data for metrics purpose, for now
storing:

• Date Time
• User Agent

Would be enough. A fingerprint for a visit could be stored on a Link History table on a
SQL relation of 1 to Many.

Currently users can create links without being authenticated.
We must encourage users to have an account in order to create links, if
theres no token present in the request, or the token belongs to a deleted
user, we must not allow link creation.

Every link must have an owner_id pointing to user ID.

In order to provide ORM ergonomics, we move from SQLx to SeaORM.

Capability to list a user's links

Comments are Posts where the parentId is specified.

Comments doesnt have a Title, different to regular posts.

When querying posts, comments should also be queried and paginated.

posts(first: 20, after: "post_xyz") {
  title
  content
  author {
    username
  }
  comments(first: 20) {
    content
    author {
      username
    }
  }
}

Change the z-index of the inputs on the post creation box

Refer #213

Currently we are allowing users to create accounts with already existent values.

When creating a link in our application, the createdAt property returns a stale date, which causes the date displayed in the link to be incorrect.

The problem is in the way the link creation date is being generated

As UI is implemented on Leptos now, we dont need to hold our pervious client using SvelteKit
anymore.

Provide support for accounts and using JSON Web Tokens for authentication.

Extend current posts query to allow users to fetch a specific user posts.

https://github.com/whizzes/gabble/blob/main/crates/server/src/graphql/modules/post/query/posts.rs#L13-L44

Capability to follow a user. This will allow users to have a personalized experience.

Tasks

Introduce the user_follow table

Introduce a user_follow table which follows the Many to Many relationship
to track user follows.

Columns would be

By using the index we avoid duplicated followers

Introduce GraphQL Operations

follow(id: Pxid): Follow

Follows the user with the provided ID and returns a Follow object which contains the operation summary.

unfollow(id: Pxid): Unfollow

Unfollows the user with the provided ID and returns a Unfollow object which contains the operation summary.

Setup a SQLite Database using SeaORM to store Links and Users.
This is a step forward to a new architecture where Links and Users are stored in a
relational database and frequently visited links are stored in Sled as a caching
strategy to speed up redirection.

I can create a link with the hash ""
should comprobate the hash

The application sorts the publications in the feed from the most current to the newest.

When a GraphQL query is executed using the filter in the user search and an invalid character is provided in the filter, the system incorrectly returns all users instead of displaying an empty result or handling the filter error properly.

query {
  user(filter: { username: "michael-liendo" }) {
    nodes {
      name
      email
      username
    }
  }
}

Expected Result:
The query should return an empty result or generate an error message indicating that the filter is invalid and cannot be applied to the user search. Alternatively, the filter error could be handled appropriately and display an informational message instead of returning all users.

Actual Result:
The query returns all existing users in the database, which is not the expected behavior.

We must make design GDPR Compliant.
https://gdpr-info.eu

Currently most of the domain logic uses unwrap for Result instances.
Instead we must propagate errors up by encouraging the use of the ? operator
and implementing Error enums based on domain logic.

The Repository trait uses an associate type to allow implementations
specifying a particular type for errors. We could use this_error crate to have
enums that we could then use on Repositories.

For instance:

UserError ->
    at: Repository -> UserError::NotFound, UserError::RepositoryError
    at: Service -> UserError::EmailTaken, UserError::WeakPassword
    at: GraphQL Interface

I think it would be good to be able to put the user name in upper or lower case, but without another one with the same name.

At the moment you can create a user in this way:

• "michael"
• "Michael"
• "michaEL".

And they would be for completely different users.

What I mean is that the user name would appear as an example:

• "Michael"

but without being able to create another user with the same characters

Hey @EstebanBorai @Michael-Liendo, feel free to submit a PR to showcase your project!

• SeaQL/sea-orm#403

Provide a Relay-compliant pagination support

rust-argon2 got a new update which makes it very slow, impacting performance and UserEx.

Refer: sru-systems/rust-argon2#52

Instead of checking manually on each request, use a GraphQL guard to perform the
checking.