https://www.prisma.io/ logo
Join Slack
Powered by
sorry stale link <https://www.prisma.io/docs/1.16/...
# orm-help
b
s
Hi Bruno - this should definitely work as you described. Let me take a look and get back to you 🙂
@Bruno Prela can you share your data model?
b
Copy code
type Example {
    id: ID! @unique
    createdAt: DateTime!
    updatedAt: DateTime!

    status: STATUS_ENUM!
    thisList: [String!]
    thatList: [String!]
}
it’s occuring for all instances of lists of strings in my data model, here is one of them (fake names), errors being generated for thisList and thatList
Copy code
The scalar field `thisList` has the wrong format: `[String!]` Possible Formats: `String`, `String!`
s
Can you change the list type to 
[String!]!
This change was introduced a while ago
b
I have another field of that type which is also giving an error
Just tried it with those fields specifically, still getting an error. Are arrays no longer supported perhaps?
j
i noticed that i always need the two 
!
on my arrays.
s
Arrays are certainly supported. But you need to use a slightly different syntax as Jared points out:
Copy code
type Example {
    id: ID! @unique
    createdAt: DateTime!
    updatedAt: DateTime!

    thisList: [String!]!
    thatList: [String!]!
}
This should work
b
I have another model like so where i also get the error:
Copy code
type MainPiece {
    id: ID! @unique
    tag: String!
    slides: [String!]!
}
and I changed them all to that syntax and still dont get it working, which version are you using @Jared
s
What issue are you getting now?
Are you able to share the full datamodel? Perhaps in a direct message?
b
it is quite big and proprietary so unfortunately I cannot, however now I just get four errors
Copy code
The scalar field `thisList` has the wrong format: `[String!]!` Possible Formats: `String`, `String!`
Does the error message perhaps give a clue to our problem?
or the version of the problem
s
I suspect you still have a wrong type in the datamodel somewhere. Upgrading from 1.9 to 1.16 is quite a big jump. You could try to create a new service and add the types a few at a time to figure out what type is causing the trouble.
@do4gr might also be able to chime in in the morning as he has a lot more experience in this area than I do.
b
ok thanks for your help ill chime in here again if i havent figured it out by the morning
j
i just tried your exact syntax and it worked. Perhaps others will have more insight
b
@sorenbs @Jared consider this resolved, my issue was related to a stale docker image 😞 sorry for wasting time
s
Happy to hear 😄
j
👍
b
I apologize, but the error did come back and was associated with whether
Copy code
migrations: false
was set or not in my docker-compose
Perhaps I misunderstood the use of migrations: false and I can only deploy with that set after I have setup my database schema and all
Open in Slack
PreviousNext
Powered by