-
Notifications
You must be signed in to change notification settings - Fork 11
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
Update master with changes in beta branch #38
base: master
Are you sure you want to change the base?
Conversation
Add config functions Update code Add data attributes Update code Update custom events Update template Remove redundant code Fix show and hide dialog functionality Remove old code Revert to .mjs Update formatting Update imports Update import Remove @types/react Update dialog Update dialog Update tablist Add parameters to function Remove redundant file Fix linter error Update test Update checked state Remove whitespaces Update yarn lock Fix linting errors Remove failing test
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.
Ik denk het wel, maar wil wel even dubbelchecken of het klopt dat cookie-consent.mjs
is verwijderd? Maar ik ken eerlijk gezegd niet alle changes in de beta
branch, dus als master
hierbij gewoon helemaal gelijk is aan beta
dan lijkt het mij helemaal dikke prima!
@MartijnNieuwenhuizen Wil jij ook nog even kijken?
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.
@JairoTheDev @harmenjanssen
I think the code changes are fine if they match with the current beta.
I can imagine some additional cleanup could be nice, but that can be out of scope for this task.
What I do think should change is the Readme. This is documentation about how to use the (when this is merged) previous version) and that won't work anymore.
I think the main documentation can stay the same, just the code examples should be different. And it should mention Custom Element somewhere :)
Because this is an public repo, I think the docs should be up-to-date.
Oh, absolutely! That's a good point. @JairoTheDev Do you feel up for it? |
Nieuwe release maken van de cookie consent met de veranderingen in de
beta
branch!@harmenjanssen Kan jij checken of dit klopt?