If you run package, a static html version of net.create is exported. Make sure this works with the new features.
Typically, we use this to make a static version for sharing publicly, so the security requirements are not as strict. Where security comes in is that we need to make sure that any changing of names ripples through. For example, if I change my name from Joshua to Student 1, that needs to update the fields, but also the update records, provenance, and comment signing that include that name.
We don't need / want to automatically change a field type (e.g., name) since we a) have time to do this by hand, b) want a record / sometimes use specific pseudonyms, and c) sometimes do not know which fields will change. For example, distant places like California we might leave, but Bloomington we'll change to "Local town."
@benloh I just tested and this appears to be working. I'm OK closing this for now and then re-visiting later if either issues arise or we need new features based on other things changing?
If you run package, a static html version of net.create is exported. Make sure this works with the new features.
Typically, we use this to make a static version for sharing publicly, so the security requirements are not as strict. Where security comes in is that we need to make sure that any changing of names ripples through. For example, if I change my name from Joshua to Student 1, that needs to update the fields, but also the update records, provenance, and comment signing that include that name.
We don't need / want to automatically change a field type (e.g., name) since we a) have time to do this by hand, b) want a record / sometimes use specific pseudonyms, and c) sometimes do not know which fields will change. For example, distant places like California we might leave, but Bloomington we'll change to "Local town."