Skip to content

Conversation

@nabinchha
Copy link
Contributor

closes #140

After fix:
Screenshot 2025-12-16 at 10 13 42 AM

Screenshot 2025-12-16 at 10 13 58 AM

@nabinchha nabinchha changed the title fix: handle of different inference params in info display fix: handling of different inference params in info display Dec 16, 2025
@nabinchha
Copy link
Contributor Author

Should we change Model ID -> Model or vice versa to stay consistent across the two tables?

Copy link
Contributor

@johnnygreco johnnygreco left a comment

Choose a reason for hiding this comment

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

sweet 🙌

@nabinchha nabinchha merged commit 796e370 into main Dec 16, 2025
15 checks passed
@nabinchha nabinchha deleted the nmulepati/fix-140-handle-inference-params-info-display branch December 16, 2025 18:12
@johnnygreco
Copy link
Contributor

Should we change Model ID -> Model or vice versa to stay consistent across the two tables?

lol just noticed this. probably should switch to model for consistency. i can update in my current PR

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.

Handle different inference params in config builder info display

3 participants