Monorepo for Tangled tangled.org

appview: allows a default knot to be configured #858

closed opened by willdot.net targeting master from [deleted fork]: master

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.

Labels

None yet.

assignee

None yet.

Participants 2
AT URI
at://did:plc:dadhhalkfcq3gucaq25hjqon/sh.tangled.repo.pull/3m7glmp44b322
+2 -2
Interdiff #0 โ†’ #1
appview/db/db.go

This file has not been changed.

appview/db/profile.go

This file has not been changed.

appview/knots/knots.go

This file has not been changed.

appview/models/profile.go

This file has not been changed.

appview/pages/pages.go

This file has not been changed.

appview/pages/templates/knots/index.html

This file has not been changed.

appview/pages/templates/repo/fork.html

This file has not been changed.

appview/pages/templates/repo/new.html

This file has not been changed.

appview/repo/repo.go

This file has not been changed.

appview/state/profile.go

This file has not been changed.

appview/state/router.go

This file has not been changed.

appview/state/state.go

This file has not been changed.

+2 -2
flake.lock
··· 99 99 "lastModified": 1731402384, 100 100 "narHash": "sha256-OwUmrPfEehLDz0fl2ChYLK8FQM2p0G1+EMrGsYEq+6g=", 101 101 "type": "tarball", 102 + "url": "https://github.com/IBM/plex/releases/download/@ibm/plex-mono@1.1.0/ibm-plex-mono.zip" 102 - "url": "https://github.com/IBM/plex/releases/download/@ibm%2Fplex-mono@1.1.0/ibm-plex-mono.zip" 103 103 }, 104 104 "original": { 105 105 "type": "tarball", 106 + "url": "https://github.com/IBM/plex/releases/download/@ibm/plex-mono@1.1.0/ibm-plex-mono.zip" 106 - "url": "https://github.com/IBM/plex/releases/download/@ibm%2Fplex-mono@1.1.0/ibm-plex-mono.zip" 107 107 } 108 108 }, 109 109 "indigo": {

History

4 rounds 8 comments
sign up or login to add to the discussion
1 commit
expand
ead0762e
appview: allows a default knot to be configured
expand 2 comments

I've fucked up @oppi.li

I had to delete my fork last week because I messed it up badly ๐Ÿ™ˆ And now I can't fix the merge conflicts.

Is there an easy way to rectify changing this PR to my new fork or should I just cut my losses and start the PR from scratch (fixing the merge conflicts by doing so)

im afraid there is no way to do that right now, probably best to open a new PR!

closed without merging
3 commits
expand
fe49521e
appview: allows a default knot to be configured
48ed4260
undo flake.lock change
3eae6087
appview: nil check when getting profile
expand 6 comments

valuable addition!

this strikes me more as a preference, i don't think this should go into the profile record however.

Do you mean the AT record or the database record?

Iโ€™m now doubting storing it in AT record because the default knot1.tangled.sh is only available in the tangled app view, not a 3rd party app view!

thanks for the work on this. comments:

  • can we squash all of this work into just one commit?
  • the PR also touches a few other template files, are these changes relevant to this addition? could we extract that to a different PR/commit?

will give this a quick test!

Oh Iโ€™m not sure why those files have changed. Iโ€™ll revert them. Probably my IDE autoformat.

Ok squashed the commits into a single commit, which also removed the random files that had been changed from the diff ๐Ÿคฃ

2 commits
expand
fe49521e
appview: allows a default knot to be configured
48ed4260
undo flake.lock change
expand 0 comments
1 commit
expand
fe49521e
appview: allows a default knot to be configured
expand 0 comments