Skip to content

Opt-Out of Web-View's Atomic CSS #101

@seanhess

Description

@seanhess

See #100. Basically, if users don't want to use the atomic CSS in web-view, or want to use an existing stylesheet, they ought to be able to without too much pain. (Note that web-view IS required, we need that type variable on View. Maybe we can come up with a way to let the user integrate with the type checker via the Reader effect or something?)

Options / ideas:

  1. Create a separate Web.Hyperbole.Minimal that does not include web-view by default.

  2. Take web-view exports out of Web.Hyperbole, and require users to add a second import:

import Web.Hyperbole
import Web.Hyperbole.View

Then the user could switch to another approach by changing the second import to Web.Hyperbole.External or something...

Are there other frameworks or projects that have figured out how to do this effectively?

Open Questions and Issues:

  1. Will the approach we use work with the forms support? We don't want them to have to re-implement them just because they aren't using atomic css.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions