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
Inside the data attribute is the actual resource collection. How can I handle this structure? Maybe with an extension?
I am using secure cookie authentication for my API. I looked it up and OpenAPI supports cookieAuth. I tried with the secure method but it did not got it working.
Is there some way to "compile" these information to a OpenAPI formatted file? Due to some security reasons I don't want to make this public on the same domain/subdomain and rather host it on a completely different server which is used for development purpose with limited web-access.
Is it possible to implement a conditional form request? I have a method which is a PUT request and this updates setup-data (which is done in steps/wizard). Inside the form request I have a match which uses an enum from the request path to check which step needs to be updated (since it seems a bit redundant to create separate endpoints for each step).
Just to give some example:
// Get the current step from the route$setupStep = request()->enum('step', SetupStep::class);
if ($setupStep === null) {
return [];
}
// Validation rules for each stepreturnmatch ($setupStep) {
SetupStep::CompanyData => [
'companyName' => [
'required',
'string',
'max:255',
'min:3',
],
],
};
I know that these are a lot of questions but I hope that someone can answer them :)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I'm fairly new to Scramble and I am currently trying to test if this package fits my expectations or implementations.
As of now I have multiple questions which I cannot answer myself:
This structure looks like this:
Inside the
data
attribute is the actual resource collection. How can I handle this structure? Maybe with an extension?secure
method but it did not got it working.match
which uses an enum from the request path to check which step needs to be updated (since it seems a bit redundant to create separate endpoints for each step).Just to give some example:
I know that these are a lot of questions but I hope that someone can answer them :)
Kind regards
Beta Was this translation helpful? Give feedback.
All reactions