Skip to content

Allow serialization of layout information to CSS #155

@alice-i-cecile

Description

@alice-i-cecile

What problem does this solve or what need does it fill?

This may be useful functionality for some users. If you care, please chime in in the comments!

What solution would you like?

Create a utility that converts from our native serialization format into CSS. Gate this behind a feature flag and point users to it in the docs.

Add tests to ensure that this continues to work.

What alternative(s) have you considered?

Status quo

Do nothing; we do not currently have users who want this functionality. Trying to build this in a vacuum is a recipe for disaster.

Feature flags

Revert the changes in #84 (and related features) in order to enable easy serialization via serde.

This litters our code base in surprising ways, and makes it very hard to alter the corresponding code structure (see #111 and #112, which were likely to support this functionality) as we must be mindful of CSS's constraints.

Additional context

This was the original intent behind the serde feature flags removed in #84 (and discussed further in #153).

Metadata

Metadata

Assignees

No one assigned

    Labels

    controversialThis work requires a heightened standard of review due to implementation or design complexitygood first issueGood for newcomers

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions