This follows on from the work carried out in #836
I've added a select box in the Knots settings page which pulls in the users knots and also adds in knot1.tangled.sh. When the user selects one of these options, it will save to their profile in the database. NOTE: I haven't yet implemented adding that to the AT record because I'm not sure on how the lexicon setup works yet!
Then when users go to create a new repo / fork, if there is a value in their profile for the default knot, then that will pre select the knot to use for the new repo / fork.
This is a duplicate of https://tangled.org/tangled.org/core/pulls/858/ which had to be closed because there were merge conflicts which couldn't be resolved due to the origin fork being deleted 🙈
@oppi.li While attempting to implement something else related to profiles, I've noticed that
UpsertProfile(...)herehttps://tangled.org/tangled.org/core/blob/master/appview/db/profile.go#L133 also gets called as part of a JS ingester here https://tangled.org/tangled.org/core/blob/master/appview/ingester.go#L352 which means theDefaultKnotfield will be overwritten with an empty string when a profile event is ingested. Am I understanding that correctly?So instead I should probably not use the
UpsertProfile(...)but use a smaller scoped function that just sets the Default Knot field?