Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[git-ref] namespaces support #152

Closed
3 tasks done
Byron opened this issue Aug 9, 2021 · 0 comments
Closed
3 tasks done

[git-ref] namespaces support #152

Byron opened this issue Aug 9, 2021 · 0 comments

Comments

@Byron
Copy link
Owner

Byron commented Aug 9, 2021

A way to configure reference namespaces on the fly, particularly useful for servers who want to limit what a client can see or edit.

  • expansion
  • prefix-iteration via namespace
  • transaction with namespace
@Byron Byron changed the title namespaces [git-ref] namespaces support Aug 9, 2021
Byron added a commit that referenced this issue Aug 9, 2021
Byron added a commit that referenced this issue Aug 9, 2021
Byron added a commit that referenced this issue Aug 9, 2021
Byron added a commit that referenced this issue Aug 9, 2021
It's a little more elaborate in the way we integrate namespaces into
edits as it's less error prone and more explicit that way.

Only server side repositories will even see (or use) this feature,
but at least it requires no special knowledge except for knowing
that you use namespaces and applying them for listings and for edits.
Byron added a commit that referenced this issue Aug 9, 2021
Byron added a commit that referenced this issue Aug 9, 2021
For now we are loud about it for the lack of a better way to do certain
transformations on windows.

The API remains the same though, assuming that eventually we will
do some rewriting and possibly return a PathBuf instead, hence 'Cow'.
Byron added a commit that referenced this issue Aug 9, 2021
It's probably best to make packed-refs optional even in the iterator
Byron added a commit that referenced this issue Aug 9, 2021
This makes using the API much easier as the caller doesn't have to
handle the case of not having packed-refs themselves.
Byron added a commit that referenced this issue Aug 9, 2021
Byron added a commit that referenced this issue Aug 9, 2021
Needed a thorough look into gits own tests just to validate
naming rules.
@Byron Byron closed this as completed Aug 10, 2021
Byron added a commit that referenced this issue Aug 10, 2021
Byron added a commit that referenced this issue Aug 10, 2021
It's implemented so that the standard preprocessing can easily be reused
which will become interesting when ref-tables are implemented.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant