Coder Social home page Coder Social logo

Comments (4)

Sairyss avatar Sairyss commented on June 14, 2024

it cannot correctly assign the property in the final class

What do you mean by that? Last time I checked it worked fine and all ids were assigned correctly.

Id lives in the child entity by design, because some entities can have a string id (like UUID), but some entities can have it as a number. Having id in a child lets you decide what type each entity needs instead of being bound to just strings.

from domain-driven-hexagon.

franco4457 avatar franco4457 commented on June 14, 2024

I am refactoring a project following the same structure that you have within the DDD folders, and in the tests where I verify the type of the id property it returns undefined.
Also when I do a console.log() of the entire object the _id property is also undefined:

User {
  _createdAt: 2023-12-27T12:10:06.546Z,
  _updatedAt: 2023-12-27T12:10:06.546Z,
  props: {
    email: '[email protected]',
    lastname: 'tester',
    name: 'test',
    password: Password {
      _value: '$2b$10$LW29SqaXA.1e/ruyZjyjNumC7cItPePd2guY9Eq3udPl62iep9l6u'
    },
    username: 'tested'
  },
  _id: undefined
}

I thought it was just my mistake, but when I ran the tests that you have in the project, the "create a user" test did not pass either, to run the tests locally I executed the command:

pnpm migration:up:tests
pnpm test

And the tests failed with:

  Create a user  I can create a user

    expect(received).toBe(expected) // Object.is equality

    Expected: "string"
    Received: "undefined"

      42 |     then('I receive my user ID', () => {
      43 |       const response = ctx.latestResponse as IdResponse;
    > 44 |       expect(typeof response.id).toBe('string');
         |                                  ^
      45 |     });

I imagine that the response.id is an extract of the created user id

from domain-driven-hexagon.

Sairyss avatar Sairyss commented on June 14, 2024

You have to run npm run test:e2e because those are e2e/integration tests.

from domain-driven-hexagon.

franco4457 avatar franco4457 commented on June 14, 2024

The tests passed when I changed the import from crypto.randomUUID to a named import from the randomUUID function.

Possibly the problem I am having is due to the version of Typescript or tsup

from domain-driven-hexagon.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.