Add ESX.GetConfig optional parameter#1667
Merged
Merged
Conversation
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR enhances the ESX.GetConfig() function to accept an optional key parameter.
When provided, the function returns a specific config value instead of the full config table.
This change maintains backward compatibility.
Motivation
Currently, to retrieve a single config value, you are forced to pull the entire Config table using ESX.GetConfig().
This is unnecessary in most cases and leads to inefficient code.
By allowing key-based access, we simplify config lookups and reduce coupling to internal config structure.
Implementation Details
Usage Example
PR Checklist