
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
A component is not guaranteed to generate an html element but in most scenario it happens.
Actually there is a way to allow a component to allow to receive undefined explicit parameters, by using
CaptureUnmatchedValues
property ofParameterAttribute
.This mechanism is sub-optimal because you can't for instance filter which attributes you'll get, it's a "catch'em all"
For advanced scenario, using a data-* attribute is very useful, the problem is that we have either to explicit define all the different attributes we want to get with explicit properties like
[Parameter] public string DataTarget { get; set; }
or we just rely on the CaptureUnmatchedValues where we can just splat the dictionary into the div @attributes
Since data-* attributes are very useful to extend a component behavior by making use of the element dataset (e.g. to alter the DOM in javascript or let another component to attach event handlers to the DOM), the component creator doesn't know which data- attribute the component user needs and so the component user is forced to wrap the component in an html element and apply the data attribute there (being it a limiting factor).
would be helpful to have a way to allow a component to receive any
data-*
attribute and not everything.Describe the solution you'd like
I can think about 2 solutions:
being able to automatically register data-attributes in ComponentBase, that would have a new exposed property
public Dictionary<string, object> DataAttributes { get; set; }
or allow to further configure the ParameterAttribute to explicit set the subset of attributes we are interested in catching (maybe using regex expression or tailoring this explicitly for data-* .
[Parameter( CaptureDataAttributes = true) ] public Dictionary<string, object>DataAttributes { get; set; }
The binding example could then have a way to bind all data attributes by using a syntax like
@attributes:data
,@data
,@data-attributes
or any other syntax that may have senseThanks
Additional context
No response
The text was updated successfully, but these errors were encountered: