1/ @Conaw really liking new CSS work you are all doing & we appreciate whenever UID's are included in HTML stream. The page UID is often included. Would be nice to get UID when HTML renders for:
+ block refs
+ attributes
+ #tags
+ and bonus, but not crucial Alias
#roamosphere
+ block refs
+ attributes
+ #tags
+ and bonus, but not crucial Alias
#roamosphere
3/ Tagged element with hash # but no UID 
4/ Block ref.. no UID for the ref
5/ Attributes.. no cigar
6/ Alias are interesting. We do get some context info about aliases in class names. But only external url is revealed because of href attr on <a>
rm-alias--external
rm-alias--page
rm-alias--block
rm-alias--block-missing
rm-alias--external
rm-alias--page
rm-alias--block
rm-alias--block-missing
7/ I thought perhaps the reason UID's are not returned is due to performance. However after working with API I don't think this is the case.
My guess is it wasn't needed until, but now they are since extensions are being developed on top of the UI by 3rd parties.
My guess is it wasn't needed until, but now they are since extensions are being developed on top of the UI by 3rd parties.
8/ Since you tweak the internal HTML, it's a good time for an internal design rule to benefit those on the outside:
RULE: When a data element from the DB is written out to HTML stream, it's UID is always included
UID's will rule the future. They need to be first class citizens.
RULE: When a data element from the DB is written out to HTML stream, it's UID is always included
UID's will rule the future. They need to be first class citizens.
9/ We hear there are new hires at Roam. This picture was smuggled out of Utah. With this kind of talent, UID richness in the HTML can't be far away.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
