Create a JSX file to render the cookie-consent wall <CookieConsent ... />

[ibrahimcesar]

Create a Component at src to be exported as default or named export?

import CookieConsent from "@nexo/cookieconsent"

or

import { CookieConsent } from "@nexo/cookieconsent"

[emadbaqeri]

Hey there, I think I can work on this. can you help me do this becuase I'm really new to opensourcing. I always love to help people and the community

[ibrahimcesar]

Hello @emadbaqeri , feel welcomed!

I have some experience but most of the team here , in Brazil, is also starting in Open Source.

Feel free to engage in Discussions, submit PRs and review code!

@tarekcampossaleh suggest we follow the structure of the original function to define the props signature for our Component:

cookieconsent/src/_cookieconsent.js

Line 225 in 0f2e9e2

var _createCookieConsentHTML = function(never_accepted, conf_params){

Something like:

<CookieConsent neverAccepted={false} options={obj} />

The snippet above is pseudo code so don't take as the way to implement.

• neverAccepted would be the props for the state of the use regarding having or not accepted the cookie consent. There are several "best practices" that advocates to neve use a boolean prop but I think this is a great case for a boolean prop since we'll decouple a state that can be represented as boolean.
• options would be an object which we'll need to define an interface and all the options to customize it.

I suggest we start implementing the boolean and then start to develop the options, since a lot is involved in this: read and write cookies etc. Please, any PR or commit place #11 somewhere and GitHub will help us keep track of it!