-
Notifications
You must be signed in to change notification settings - Fork 26
Feature/filament cookies #87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
sten
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, @sevbesau!
kan je nog naar de kleine opmerkingen kijken?
@kristofser kijk je ook nog even na?
| { | ||
| "/public/js/cookie-consent.js": "/public/js/cookie-consent.js", | ||
| "/public/js/cookie-consent-default.js": "/public/js/cookie-consent-default.js", | ||
| "/public/js/cookie-consent-filament.js": "/public/js/cookie-consent-filament.js", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Kan dat kwaad dat die hier allebei staan? Misschien ook in readme zetten dat ze die verwijderen afhankelijk van de theme?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mix-manifest.json is auto-generated tijdens de build van de package. Dus niet de bedoeling dat we deze manueel gaan bewerken.
In principe is het de bedoeling dat onze package pre-built js files aanbied aan de consumer en niet de bedoeling dat de end user in zijn vendor map changes moet maken om dan de juiste theme files te builden.
That said, deze mix manifest klopt wel nog niet zie ik, vergeten een nieuwe build te maken na onze changes donderdag, so fixed that!
|
@sten Merci voor je feedback. Heb je puntjes verwerkt. Kijk je nog eens na? 😄 |
Description
Created an alternative theme that uses filament components