Pere Lev
44d66c883c
S2S: Project: Remove: Implement component-active mode
2024-05-28 00:03:47 +03:00
Pere Lev
185047ecb4
S2S: Component: Remove: Implement component mode, updated process
2024-05-27 18:40:20 +03:00
Pere Lev
4838a131b4
S2S: Group: Grant: Extend Grants from my projects
2024-05-27 09:18:33 +03:00
Pere Lev
14ff1b293f
S2S: Project: Grant: When adding component/child, extend Grant to teams
2024-05-21 02:47:54 +03:00
Pere Lev
3fb5e92f44
S2S: Project: Accept: When removing a child, revoke extensions to teams
2024-05-21 02:15:14 +03:00
Pere Lev
4f5954de7e
Serve live URIs for Team (Squad) records for project, repo, deck, loom
2024-05-20 20:39:05 +03:00
Pere Lev
646e17fa56
S2S: Project: Revoke: Implement component & team modes
2024-05-18 21:56:51 +03:00
Pere Lev
3e110ca53c
UI: Group: Display resources, invites and action buttons
2024-05-18 14:11:39 +03:00
Pere Lev
e542c7d531
UI: Group: POST handlers for resource add-approve-remove buttons
2024-05-18 13:44:55 +03:00
Pere Lev
f93f67a098
UI, Vocab: Group: Serve accessible resources collection
2024-05-18 13:16:20 +03:00
Pere Lev
0ee94afd9e
UI: Component, Project: Display teams, invites and action buttons
2024-05-18 03:40:34 +03:00
Pere Lev
97dee05af8
UI: Repo, Loom: Update collaborators view & buttons, similar to Deck
2024-05-18 00:46:03 +03:00
Pere Lev
5c6e73a3d4
UI: Deck, Group, Project: Enhance collaborators view, prepare to add teams
2024-05-16 15:19:01 +03:00
Pere Lev
7ade4984d7
UI: Component: POST handlers for team add/approve/remove buttons
2024-05-15 14:23:57 +03:00
Pere Lev
6de8ce6b25
Vocab, UI: Component: Specify and serve teams collection
2024-05-15 13:51:09 +03:00
Pere Lev
46cb13e5b0
DB: Add tables for tracking project extending delegations to teams
2024-05-14 23:14:12 +03:00
Pere Lev
d23144e2c4
DB: Add tables for team-resource link tracking
2024-05-14 21:29:28 +03:00
Pere Lev
248ed1f19f
S2S: Group: Grant: Fix bug in Grant parsing
2024-05-14 13:41:50 +03:00
Pere Lev
6cb1c11141
S2S: Group: Port Revoke handler from Project
2024-05-14 13:15:16 +03:00
Pere Lev
1e69a6e952
S2S: Group: Remove: Port parent-child modes from Project
2024-05-14 12:58:46 +03:00
Pere Lev
5e0a2e1088
S2S: Group: Grant: Port parent-child modes from Project
2024-05-14 01:43:41 +03:00
Pere Lev
d72e06727c
S2S: Group: Accept: Port child-parent modes from Project
2024-05-13 02:03:58 +03:00
Pere Lev
ee30cb9f70
S2S: Project: Accept: Separate child and parent modes' code
2024-05-13 01:08:47 +03:00
Pere Lev
3162a6ac28
S2S: Group: Implement Add handler based on Project
2024-05-12 22:24:07 +03:00
Pere Lev
bef8a77d84
UI: Browse: List team parents
2024-05-12 21:46:34 +03:00
Pere Lev
74af2ea223
UI: Group: Display parent and child invites & approve-remove buttons
2024-05-12 20:15:53 +03:00
Pere Lev
533fc60fe1
UI: Group: Implement parent/child process button POST handlers
2024-05-12 19:38:50 +03:00
Pere Lev
66c1818fcd
Client: Use the new Add-based version of adding a component
2024-05-12 18:11:17 +03:00
Pere Lev
f6dda396dd
S2S: Project: Add: Implement Add-based version of projectInvite
2024-05-12 17:50:18 +03:00
Pere Lev
f864274ff0
S2S: Component: Implement Add-based version of inviteComponent
2024-05-11 22:25:50 +03:00
Pere Lev
38ce72996c
Port deckAdd to be a reusable componentAdd
2024-05-05 23:38:58 +03:00
Pere Lev
4b6e95b2e8
DB: Remove StemIdent* tables, use Komponent instead
2024-04-30 00:32:30 +03:00
Pere Lev
5d594ca738
DB: Remove ComponentLocal* tables, use Komponent instead
2024-04-29 23:23:59 +03:00
Pere Lev
aeb1a83c93
DB: Add a Komponent record, to gather local repos/decks/looms/etc.
2024-04-29 14:38:37 +03:00
Pere Lev
1d08e43175
CSS: Tweak styling of buttons, fixing the clipped button bug
2024-04-29 13:41:51 +03:00
Pere Lev
42b83c11f9
UI: Deck: Projects: Button for removal
2024-04-29 13:26:15 +03:00
Pere Lev
9646b72ded
UI: Project: Components: Button for removal
2024-04-29 11:32:11 +03:00
Pere Lev
12ea0c021e
UI: Deck: Projects: More detailed table + button for approving
2024-04-29 11:01:33 +03:00
Pere Lev
ca6aa718f6
UI: Project: Components: More detailed table + button for approving
2024-04-29 09:58:04 +03:00
Pere Lev
ffe1c39fd3
UI: Deck: Form for adding to a project
2024-04-29 02:08:44 +03:00
Pere Lev
d04f161203
UI, Client: Move invite-component form to ProjectComponentsR and use getCapability
2024-04-29 01:14:56 +03:00
Pere Lev
6cdd332d1d
UI: Remote actor view + follow UI
2024-04-28 21:08:04 +03:00
Pere Lev
a428bd74ab
UI, S2S: Store errors in Errbox + display in notifications
2024-04-28 00:31:48 +03:00
Pere Lev
a60b05b1ca
UI: Error-inbox ("Errbox") display for all local actors
2024-04-27 23:17:22 +03:00
Pere Lev
29e7581b19
DB: Give each actor a secondary inbox, for collecting errors
2024-04-27 22:46:37 +03:00
Pere Lev
ef036fd08b
UI: Project: Parents: Button for approving a parent
2024-04-27 22:02:40 +03:00
Pere Lev
99f6d950a2
UI: Project: Parents: Form for adding a parent by URI
2024-04-27 21:46:49 +03:00
Pere Lev
082eae7a51
UI: Project: Children: Button for approving the Add
2024-04-27 21:37:13 +03:00
Pere Lev
d9d6b9fced
UI: Project: Children: Form for adding a child
2024-04-27 20:58:26 +03:00
Pere Lev
9e24038ec2
Deliver activities to remote audience before local+collections
...
This is an attempt to prevent remote activities from being received in
the wrong order, for example Accept coming before the Add. Whenever that
happens, the add-a-child-parent-link process cannot be completed.
If this doesn't help, another option is to store, per actor, a list of
activities that weren't used, and check them in relevant S2S handlers.
This might have an implication on forwarding if it's time limited (I
don't remember exactly). But worth trying. Example:
- I receive an Accept on an activity I don't recognize
- I store it in that list, for later
- Later I receive an Add activity, which I successfully process
- Now I check that Accept from earlier, seeing if its `object` happens
to be the Add I just received
- If yes, I now process this Accept
A potential problem with this, is that I might accumulate a list of such
activities, and end up hopelessly checking them in every S2S handler.
And I wonde if this is really a healthy elegant approach to the ordering
problem. Maybe some sort of activity numbering can help?
2024-04-27 20:13:01 +03:00
