Coder Social home page Coder Social logo

oma's People

Contributors

andershansander avatar d-pixie avatar dependabot[bot] avatar ehannes avatar johalv avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar

oma's Issues

Add support for multiple oma-google-calendar on one page

Currently, only one oma-google-calendar is supported on a page due to this code:

const getElementByDataHandle = (handle) =>
  document.querySelector('[data-handle="' + handle + '"]')
const contentSwitch = getElementByDataHandle('oma-google-calendar')

Instead of searching the whole document, we should search within the component.

FOUC

The current solution for setting stylesheet rules creates a lot of FOUC. They are written in a useEffect hook, like this:

  useEffect(() => {
    State.stylesheet.write()
  })

This is problematic, especially for components like oma-site which is not completely rendered before all things inside it is rendered. That means, we are basically writing the Oma stylesheet on DOMContentLoaded, which is terribly late in the rendering process! In oma-site, we set a lot of custom properties that we use on a lot of places. Until the component is rendered, these custom properties are undefined...

Our default breakpoints are working a lot better though, they are not run inside useEffect.

HTTP link missing styles

The HTTP link should make use of the internal LinkTag component. I just don't know how to pass the slot content to that component...

State not working

When importing State with: import { State } from '@oma-wc/state', the built code produces this error:

Uncaught TypeError: Class constructor Singleton cannot be invoked without 'new'

This is the built code that raises the error:

const State$1 = Singleton();

The weird thing is that this code is also present in other packages builds, so I have no idea why only this package build produces this error.

Uncaught ReferenceError: exports is not defined

The CommonJS version of the internal/common/state component is broken. The line Object.defineProperty(exports, '__esModule', { value: true }); in the build code gives the following error when included as a script:

Uncaught ReferenceError: exports is not defined

Uncaught error for non phone numbers

We have missed to check if the phone number parses correctly. We get Uncaught (in promise) TypeError: Cannot read property 'isValid' of undefined

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.