Bird87ZA
Repos
9
Followers
6
Following
7

Events

Created at 1 week ago

Change to how multipart is built

Created at 1 month ago

Better handling of multipart

Created at 1 month ago

Updated paths, added interface, added file handling

Created at 1 month ago
Bird87ZA create branch add-embedding
Created at 1 month ago

Change serialization to json encoding

Created at 1 month ago

Only store the state of public fiends

Created at 1 month ago
Bird87ZA create branch add-persisted-state
Created at 1 month ago
Bird87ZA create branch fix-forstep-bug
Created at 1 month ago
Bird87ZA delete branch fix-forstep-bug
Created at 1 month ago
pull request closed
Fixed an issue where forStep returns general state

Fix for potential issue discussed here https://github.com/spatie/laravel-livewire-wizard/discussions/46

Created at 1 month ago
Fixed an issue where forStep returns general state

Seems it's not a code issue...

Created at 1 month ago
pull request opened
Fixed an issue where forStep returns general state

Fix for potential issue discussed here

Created at 1 month ago
pull request closed
Fixed an issue where forStep returns general state
Created at 1 month ago
pull request opened
Fixed an issue where forStep returns general state
Created at 1 month ago
Bird87ZA create branch fix-forstep-bug
Created at 1 month ago
create tag
Bird87ZA create tag v0.2.4
Created at 1 month ago

Bookings pushback (#12)

  • Added reservation push back handlers in mmk

  • Added the service

  • Changed to a slice of pointers

  • Made MMKDateTime default

  • Fixed typo

  • Get value, not address

  • Get value, not address

  • Initialize Reservations differently

  • Added price service

  • Get value, not address

  • Added Pricing; fixed minor issues

Co-authored-by: Victor Hugo Avelar Ossorio deltatuts@gmail.com

Created at 1 month ago
delete branch
Bird87ZA delete branch bookings-pushback
Created at 1 month ago
pull request closed
Bookings pushback

Description

Describe your changes in detail.

Motivation and context

Why is this change required? What problem does it solve?

If it fixes an open issue, please link to the issue here (if you write fixes #num or closes #num, the issue will be automatically closed when the pull is accepted.)

How has this been tested?

Please describe in detail how you tested your changes.

Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc.

Screenshots (if appropriate)

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

  • [ ] Bug fix (non-breaking change which fixes an issue)
  • [ ] New feature (non-breaking change which adds functionality)
  • [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

Go over all the following points, and put an x in all the boxes that apply.

Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our continuous integration server to make sure your tests and code style pass.

  • [ ] I have read the CONTRIBUTING document.
  • [ ] My pull request addresses exactly one patch/feature.
  • [ ] I have created a branch for this patch/feature.
  • [ ] Each individual commit in the pull request is meaningful.
  • [ ] I have added tests to cover my changes.
  • [ ] If my change requires a change to the documentation, I have updated it accordingly.

If you're unsure about any of these, don't hesitate to ask. We're here to help!

Created at 1 month ago
pull request opened
Bookings pushback

Description

Describe your changes in detail.

Motivation and context

Why is this change required? What problem does it solve?

If it fixes an open issue, please link to the issue here (if you write fixes #num or closes #num, the issue will be automatically closed when the pull is accepted.)

How has this been tested?

Please describe in detail how you tested your changes.

Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc.

Screenshots (if appropriate)

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

  • [ ] Bug fix (non-breaking change which fixes an issue)
  • [ ] New feature (non-breaking change which adds functionality)
  • [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

Go over all the following points, and put an x in all the boxes that apply.

Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our continuous integration server to make sure your tests and code style pass.

  • [ ] I have read the CONTRIBUTING document.
  • [ ] My pull request addresses exactly one patch/feature.
  • [ ] I have created a branch for this patch/feature.
  • [ ] Each individual commit in the pull request is meaningful.
  • [ ] I have added tests to cover my changes.
  • [ ] If my change requires a change to the documentation, I have updated it accordingly.

If you're unsure about any of these, don't hesitate to ask. We're here to help!

Created at 1 month ago

Added Pricing; fixed minor issues

Created at 1 month ago

Get value, not address

Created at 1 month ago

Added price service

Created at 1 month ago

Initialize Reservations differently

Created at 1 month ago

Get value, not address

Created at 1 month ago