-
Notifications
You must be signed in to change notification settings - Fork 99
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
Support for new stream subject transform functionalities #695
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let some small comments, I need to see how this looks to really review the UX changes, will look fridayish.
901e76e
to
7bd478a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some small comments, need more time to run it and see how the UX feels
If you update to latest fisk release I think it will now do some dynamic column width adjustment and on larger displays no more wrapping of flags such that we have 10 more chars to play with for long flags. Update to that lets see how it looks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very close now, this is amazing stuff really love it
I have one general usability comment: Given a stream with subjects I think probably the stream should be found by the fact that it holds those messages? Probably a server thing and maybe not fixable but just a weird UX thing I noticed that we might think about |
About the general usability comment: yes the current Stream subject transform is a bit the final nail in that coffin, but trying to find the stream from just the subject you subscribe to is fundamentally wrong now, even if you tried to look at the subjects of the messages in the stream (can't just look at the current transform as that also can change over the lifespan of the stream) you can have more than one stream with messages on a particular subject and there's no way the subscribe would be able to know which of those streams you actually want to consume from. The proper/actual solution to this is already in the works: the JS simplification effort where the JS API no longer try to find the stream from the subject you subscribe to but rather the new simplified JS API requires you explicitly pass the stream name to create a consumer on it. |
2af2c5d
to
ef7a92f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a few comments, I see some earlier ones also still outstanding, looking good!
ef7a92f
to
a0178a4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good, just remove all the redundant humanize calls.
Only time we need them now is with AddRowf()
b7685c5
to
43885f0
Compare
c7c6121
to
a3e7441
Compare
3bff9a0
to
d3a2e1f
Compare
@jnmoyne how are we on this? Can you rebase? People desperate for the CLI release so I want to get this one in. |
0cb75cd
to
2e94251
Compare
I'd also like to get this one finally merged :). Actually rebased yet again 5 days ago but yeah needed another one since, which is done now. |
The status is that it's still good to go. Since that PR was created there's been additional functionality (i.e. multi subject support) in stream sources and mirroring which this doesn't cover as I'd rather create a new PR for those. If you'd prefer I did those changes in new commits to this branch instead let me know. |
Unfortunately looks like latest clean up introduced a number of formatting bugs and code layout changes etc, left some comments there. Is the server work in 2.10 now done and merged completely? I prefer smaller PRs for sure. so do not want to add to this. Even this I'd have done as many PRs rather than a huge singe PR :) |
Remove redundant humanize Make a few things consistent and cleanup a couple redundancies from the merge Implement PR feedback Source details made more compact Make test check for both arguments being non-null to improve readability Adds lag/last seen/external/error for sources in KV info improve stream report Rebase merge from main
Add empty lines around control statements to improve readability Update go.mod for nats.go to the 2.10.0 branch current latest commit
a9d446b
to
e0237b0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
small changes left
Clean up republish flag Simplify and fix config checking for republish Add empty lines around control statements to improve readability Update go.mod for nats.go to be able to build
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
very very close now :)
Improved checking of republish and transform arguments being passed in create, copy and edit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Support for the new stream subject transform functionalities: