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

348 alternative testing #546

Merged
merged 12 commits into from
Mar 15, 2023
Merged

348 alternative testing #546

merged 12 commits into from
Mar 15, 2023

Conversation

vanessuniq
Copy link
Contributor

No description provided.

@vanessuniq vanessuniq temporarily deployed to vulcan-pr-546 March 13, 2023 18:35 Inactive
@vanessuniq
Copy link
Contributor Author

PR this because it's much cleaner to focus only on the component.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Line 295: General rule, if you are uncertain whether the record exists or not, use find_by and handle the nil case, and if you are confident that the record exists, use find.
using find raises an exception if the record is not found, which can impact performance and create unnecessary overhead in the application, even though the exception is handled.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Also, we can't see the rule direct link when on edit mode. not sure if that's the intent.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The rule direct link is at the bottom of the page, not quite noticeable. I think it will be better to have it at the top.

@@ -24,6 +25,34 @@ def index
@components_json = Component.eager_load(:based_on).where(released: true).to_json
end

def set_rule
Copy link
Contributor Author

Choose a reason for hiding this comment

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

this must be a private method

Signed-off-by: Vanessa Fotso <[email protected]>
@vanessuniq vanessuniq temporarily deployed to vulcan-pr-546 March 14, 2023 04:02 Inactive
@vanessuniq vanessuniq linked an issue Mar 14, 2023 that may be closed by this pull request
@vanessuniq vanessuniq temporarily deployed to vulcan-pr-546 March 14, 2023 21:55 Inactive
@vanessuniq vanessuniq temporarily deployed to vulcan-pr-546 March 14, 2023 22:13 Inactive
@freddyfeelgood
Copy link
Contributor

Also, during testing we discovered that it appears we've broken the top right "Search by SRG Version" functionality. It still searches, and navigates when selecting an item, but the selected item is not "pre-selected" like it used to be.

@vanessuniq
Copy link
Contributor Author

looks clean to me

@vanessuniq vanessuniq temporarily deployed to vulcan-pr-546 March 15, 2023 14:37 Inactive
@vanessuniq vanessuniq temporarily deployed to vulcan-pr-546 March 15, 2023 15:52 Inactive
@vanessuniq vanessuniq enabled auto-merge (squash) March 15, 2023 16:06
Copy link
Contributor

@freddyfeelgood freddyfeelgood left a comment

Choose a reason for hiding this comment

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

Approving for deep linking functionality.

@vanessuniq vanessuniq merged commit 1a83548 into master Mar 15, 2023
@vanessuniq vanessuniq deleted the 348-alternative-testing branch March 15, 2023 16:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Merged
Development

Successfully merging this pull request may close these issues.

Add deep linking to controls
2 participants