Giter VIP home page Giter VIP logo

client's People

Contributors

caiogrossi avatar diegodsgarcia avatar eriksongoncalves avatar felipe-jm avatar gfgabrielfranca avatar guilleangulo avatar guilouro avatar guissalustiano avatar jeffersonbraster avatar lucasnfuzeto avatar luizeboli avatar lukazovic avatar morpa avatar rodrigocan avatar williamrmendonca avatar willianjusten avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

client's Issues

Comparação create-payment-intent

Toda vez que você atualiza o carinho criar uma nova intenção de compra, se faço isso propositalmente gera vários payment intent ,com meta dados não tem como eu verifica se o mesmo usuário criou um payment intent idêntica.

Local de favicon e manifest

<link rel="shortcut icon" href="/img/icon-512.png" />
<link rel="apple-touch-icon" href="/img/icon-512.png" />
<link rel="manifest" href="/manifest.json" />

Estava analisando a documentação do Next.js para entender a diferença do Head no _app e no _document, pelo que entendi tudo que é "global" para todas as páginas deve ser no _document e tudo que é "único" deve ser em específico para cada página.

"The component used here _(document) is not the same one from next/head. The component used here should only be used for any code that is common for all pages. For all other cases, such as <title> tags, we recommend using next/head in your pages or components."

Procurei para ver como utilizam no site do Next: https://github.com/vercel/next-site/blob/master/pages/_document.js

Neste caso favicons, scripts (Google Analytics...), manifest e outros itens do gênero ficariam no _document, correto? É algo indiferente?

Who to contact for security issues

Hello 👋

I run a security community that finds and fixes vulnerabilities in OSS. A researcher (@keatonfisher) has found a potential issue, which I would be eager to share with you.

Could you add a SECURITY.md file with an e-mail address for me to send further details to? GitHub recommends a security policy to ensure issues are responsibly disclosed, and it would help direct researchers in the future.

Looking forward to hearing from you 👍

(cc @huntr-helper)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.