What functionality are you missing in the framework?

[reindert-vetter]

What functionality are you missing in the framework? I am now thinking of building Rate Limiting. But what do you need? Functions are fully implemented in one go as much as possible.

[Wulfheart]

I really like the Livewire stuff in Laravel but this is more a package for userland.
Components in templates would be nice though.

Furthermore:

• Auth scaffolding (maybe something like Fortify?)

[NWBY]

Rate limiting seems like a good idea. A few things that come to mind are:

• Custom helpers
• Webpack support (I believe this could easily be achieved by using Laravel Mix)
• DB and ORM setup

Apologies if any of these have already been implemented.

[reindert-vetter]

That looks good. Thanks! I have created a new discussion for custom helpers:
#102

[reindert-vetter]

• Webpack support

New discussion:
#104

[Wulfheart]

Any ETA for generics in Go?

[reindert-vetter]

@Wulfheart ~End of this year.

[reindert-vetter]

New ORM discussion: #110

[rafaelbreno]

• The validation section could be more in depth
  • E.g. the "unique" key, if you open a issue I could help adding more validations, implementing TDD in those new features
• CMD commands to generate pre-defined files
• Queues/Jobs

[reindert-vetter]

Great that you want to help! Besides the documentation you can obviously see how other rules are implemented.
You can use issue confetti-framework/validation#1

[almas1992]

Great that you want to help! Besides the documentation you can obviously see how other rules are implemented.
You can use issue confetti-framework/validation#1

Speaking of validation, Is there any plan to add Validate method for request ?
example

failures := request.Validate(
    val.Verify("name", rule.Required{}, rule.String{}),
    val.Verify("email", rule.Required{}, rule.Email{}),
)

[reindert-vetter]

That is nice indeed, but it is not possible to validate the parameters in that way. But maybe that's not so bad.

I also wanted to make the interface of request as small as possible (it will be easier to mock). But I can see that this is very useful. What do others think about this?

[bosix]

Scheduling and async job execution are really great in laravel (https://laravel.com/docs/8.x/scheduling). Would love to see it in confetti.

I suggest a queue-worker system for job execution that utilizes goroutines for parallel execution and a worker pool to prevent too many jobs from being executed at the same time.

[almas1992]

How about anonymous validation function, easy to define custom validation rules
example

type VerifyFunc func(value support.Value) error

func (f VerifyFunc) Verify(value support.Value) error {
	return f(value)
}

failures := val.Validate(app, content,
		val.Verify("some.field", val.VerifyFunc(func(value support.Value) error {
                        // do awesome validation
			return nil
		})))

[reindert-vetter]

That is indeed a very good idea and easy to implement. Way not:

failures := val.Validate(app, content,
val.Verify("some.field", func(value support.Value) error {
         // do awesome validation
	return nil
}))

Then that interface must be made smaller, but than it is the same as Laravel.

https://laravel.com/docs/8.x/validation#using-closures

[almas1992]

Because that val.Verify received a inter.Rule interface, not the anonymous function. However val.VerifyFunc can convert
anonymous function to inter.Rule interface. In this way you don't need change any code in val.Verify method.

[nurmuhammet-ali]

Could be better if documentation had "Deployment" block