You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My team and I are having a strange problem with the paths, for me the import must follow one order and for the rest of the team another, and it is only for me that the order is different.
This is my problem:
import { TableOrderComponent } from "src/app/shared/tables/table-order/table-order.cmponent";
import { TableOrderDetailsComponent } from "src/app/shared/tables/table-order-details/table-order-details.cmponent";
It asks me to change the order, passing TableOrderDetails above TableOrder, but my colleagues say the "correct" order is the one in the code above.
@thiagosauddev the solution would be, waiting for that PR to land and be released.
While using aliases is a neutral practice, using @alias specifically is a bad practice, since a leading @ means "an npm scope". You should pick a character that doesn't already mean something else.
My team and I are having a strange problem with the paths, for me the import must follow one order and for the rest of the team another, and it is only for me that the order is different.
This is my problem:
It asks me to change the order, passing TableOrderDetails above TableOrder, but my colleagues say the "correct" order is the one in the code above.
TSCONFIG:
ESLINT:
LIBS:
The text was updated successfully, but these errors were encountered: