Skip to content

Response and Commit to open fields position swaped in LT table#586

Merged
jayantbh merged 6 commits intomiddlewarehq:mainfrom
sahitya-chandra:LT-table-fields-swap
Oct 10, 2024
Merged

Response and Commit to open fields position swaped in LT table#586
jayantbh merged 6 commits intomiddlewarehq:mainfrom
sahitya-chandra:LT-table-fields-swap

Conversation

@sahitya-chandra
Copy link
Contributor

@sahitya-chandra sahitya-chandra commented Oct 10, 2024

resolved #547

Screenshot from 2024-10-10 19-20-55

@CLAassistant
Copy link

CLAassistant commented Oct 10, 2024

CLA assistant check
All committers have signed the CLA.

@jayantbh
Copy link
Member

I think you can remove "good first issue" from the title. 👍

@jayantbh
Copy link
Member

Could you share a screenshot of you reproducing the issue by yourself and then the fix?

Currently the issue screenshot is from the original reporter, and contains a different selection of columns and data which makes it a slightly less than a 1:1 comparison.

In terms of the code change itself, I think it's sound and needs no further changes.

@sahitya-chandra sahitya-chandra changed the title good first issue: Response and Commit to open fields position swaped in LT table Response and Commit to open fields position swaped in LT table Oct 10, 2024
@sahitya-chandra
Copy link
Contributor Author

@jayantbh This is a current screenshot of the issue

Screenshot from 2024-10-10 21-36-12

@jayantbh
Copy link
Member

If that's a screenshot of the issue, what does the fix look like?

@sahitya-chandra
Copy link
Contributor Author

sahitya-chandra commented Oct 10, 2024

The fix is just to swap response and commit to open fields in the table.
because the order of data is (commit -> response)

@jayantbh
Copy link
Member

I understand, but generally it's a good idea to show visual example of the fix.

For example, what the issue looked like before, and how your change impacted it. :)

It makes it easier for a reviewer to review and approve your PR, and improves trust in your PRs. 🚀

Given that the response times don't seem to exist in those PRs, you could sync another repo with PR activity, such as Middleware itself.

@sahitya-chandra
Copy link
Contributor Author

Ok sir i will do it right away

@sahitya-chandra
Copy link
Contributor Author

Previous
Screenshot from 2024-10-10 22-02-29
Screenshot from 2024-10-10 22-02-37

After:
Screenshot from 2024-10-10 22-03-10
Screenshot from 2024-10-10 22-03-18

Sir have a look

@jayantbh
Copy link
Member

It seems that the issue isn't completely resolved. You see how commits, lines, and comments are all showing time units even after your change?

They should be some number values. Basically it seems like multiple headers aren't set in the correct order w.r.t. their body columns. You would need to address those as well to fully fix this.

@jayantbh
Copy link
Member

jayantbh commented Oct 10, 2024

Unrelated... I'm finding it curious about why the response, commit to open, and other times aren't showing up. Is that a different bug? @adnanhashmi09 @samad-yar-khan

@sahitya-chandra
Copy link
Contributor Author

previously i was applying filter in configure options that's why the numbers were not showing

Screenshot from 2024-10-10 22-13-48

@jayantbh
Copy link
Member

Oh that is strange, because the headers should also hide if you unselect the columns from configure columns.

Is that not what's happening?

@sahitya-chandra
Copy link
Contributor Author

No sir, when i unselect commits or lines their header keeps on showing

@sahitya-chandra
Copy link
Contributor Author

@jayantbh Sir in 2nd commit I have fixed unhiding issue of column when unselected in configure columns.

Screencast.from.2024-10-10.23-00-05.webm

@jayantbh
Copy link
Member

Ah, that's more like it. Thanks for sorting that out.
I believe the files aren't properly linted though. Could you run the linter? You'll find instructions in the contributing guide.

@sahitya-chandra
Copy link
Contributor Author

sure sir

@sahitya-chandra
Copy link
Contributor Author

Sir, linting done

@jayantbh
Copy link
Member

Hey again, so sorry this is one last trivial thing left.
The commands in the contributing guide don't use the --frozen-lockfile flag as they should, resulting in changes to package.json and yarn.lock.

Could you undo changes to those files and push again?

I think the rest is good to go.

@jayantbh
Copy link
Member

The linter still failed after your last change. Check the above checks.

@sahitya-chandra
Copy link
Contributor Author

sahitya-chandra commented Oct 10, 2024

  • All checks passed

  • Linting completed

checked={allPrsSelected}
indeterminate={somePrsSelected}
onChange={(e) => {
onChange={(e: any) => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't use any.
Identify what the right type for this will be. Leverage the powers that Typescript offers.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I didn't miss this earlier, I'd have approved it this time.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sir, I have added the correct type now

@jayantbh
Copy link
Member

That's it! Done! Great work @sahitya-chandra! Hopefully your subsequent PRs will go smoother. :)

@jayantbh jayantbh merged commit deec257 into middlewarehq:main Oct 10, 2024
@sahitya-chandra
Copy link
Contributor Author

sahitya-chandra commented Oct 10, 2024

That's it! Done! Great work @sahitya-chandra! Hopefully your subsequent PRs will go smoother. :)

Learn a lot this time
Thanks @jayantbh sir for your support
and the PR will surely go very smooth in future

@sahitya-chandra sahitya-chandra deleted the LT-table-fields-swap branch October 11, 2024 04:58
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

Successfully merging this pull request may close these issues.

Response and Commit to Open Appear to be Swapped

3 participants