Skip to content

Consider a way to avoid duplication for entries that share compat data #813

@ddbeck

Description

@ddbeck

From comments on #725, about avoiding duplication when data is duplicated between entries that differ only in name:

@ddbeck:

It might be nice to some day have this package to allow a sort of "see also" format (something like { "__compat": { "see": "css.properties.some_prop" } }) to avoid the duplication, though hashing out what that's supposed to mean exactly might be complicated. Should I open an issue for that or is it too rare to matter?

@Elchi3:

I think the "see also" format is interesting. For APIs, there are sometimes entire feature trees that have the same compat data and we're repeating this info leading to some giant JSON files. On the other hand, and from a data consumer point of view, I feel like I don't want to deal with yet another thing to resolve for displaying the data :-) File an issue, good to have a discussion about this on record.

Metadata

Metadata

Assignees

No one assigned

    Labels

    infraInfrastructure issues (npm, GitHub Actions, releases) of this project

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions