-
Notifications
You must be signed in to change notification settings - Fork 68
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
Make flagext
pkg consistent across different projects
#32
Comments
You mean to port improvements from Loki's flagext package to dskit? |
Yes!. that's right. Would be great if all GL projects (like Loki, Tempo, Cortex) uses same flagext package. |
@kavirajk The flagext from Cortex was already ported to dskit. What specifically is the one in dskit missing compared to loki's copy? I'm closing this since Loki has already been updated to use the version from DSKit: grafana/loki#4225 |
@56quarters Loki still have its custom version of flagext (already mentioned in the description) and its still using it. My point is we should bring that also into dskit. And Loki should use only flagext from dskit!. |
I think it depends on what we wanna port. Is the data type specific to Loki? Then I would keep it in Loki. Is the data type generic (ex. human bytes) then we can move it to dskit if can benefit other projects too. |
Currently Loki uses, its own version of
flagext
packageShould we also bring this to dskit?
One of the rationale from my side personally is, it will make entitlement system validation simpler. Having it in single place. e.g: I can implement custom JSON unmarshalling for these types in one place.
The text was updated successfully, but these errors were encountered: