plumatic-schema | 易学教程

Validating multiple polymorphic values using Prismatic Schema

阅读更多关于 Validating multiple polymorphic values using Prismatic Schema

问题 A little while ago I asked about simple polymorphic schemas, and the answer there worked well for a time. Now the map I wish to validate has an additional value which is dependent upon another key's value. A contrived example of the object: {:type :foo {:type :bert {:type :foo :foo-param :bar :bert-size :medium :foo-param :bar :method :baz :method :baz :method :bang :baz-rate :max} :baz-rate :max} :bangness :considerable} The discriminators here are :type and :method , each of which has its

Non-required arguments in compojure-api/schema/swagger?

阅读更多关于 Non-required arguments in compojure-api/schema/swagger?

问题 When I have a definition of an API like this: (POST* "/register" [] :body-params [username :- String, password :- String, name :- String] (ok))) what's the appropriate way of making name optional? Is it: (POST* "/register" [] :body-params [username :- String, password :- String, {name :- String nil}] (ok))) 回答1: As you know it uses letk plumbing notation and as far as I recall the syntax is correct but the default value should be consistent with the expected type so I'd say it should be ""

Non-required arguments in compojure-api/schema/swagger?

阅读更多关于 Non-required arguments in compojure-api/schema/swagger?

When I have a definition of an API like this: (POST* "/register" [] :body-params [username :- String, password :- String, name :- String] (ok))) what's the appropriate way of making name optional? Is it: (POST* "/register" [] :body-params [username :- String, password :- String, {name :- String nil}] (ok))) As you know it uses letk plumbing notation and as far as I recall the syntax is correct but the default value should be consistent with the expected type so I'd say it should be "" rather than nil as (string? nil) => false (POST* "/register" [] :body-params [username :- String, password :-

Prisma data modeling has many and belongs to

阅读更多关于 Prisma data modeling has many and belongs to

I have a prisma data model that consists of a root Category and a Subcategory. A Category has many Subcategories and a Subcategory belongs to one Category. My model looks like this: type Category { id: ID! @unique createdAt: DateTime! updatedAt: DateTime! name: String! subCategories: [SubCategory!]! @relation(name: "Subcategories") } type SubCategory { id: ID! @unique createdAt: DateTime! updatedAt: DateTime! name: String! category: Category! @relation(name: "ParentCategory") cards: [Card!]! @relation(name: "SubCategoryCards") #Category @relation(name: "CardCategory") } Now when i go to create